Introduce content paths update functionallity #4677
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
barryyosi-panw
force-pushed
the
support-content-path-dynamic-update-2
branch
from
bda8a6a to
f8125f3
Compare
barryyosi-panw
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issues
fixes: CIAC-12161
Description
Within the content contributions-flow, the
ValidateContentscript uses demisto-sdk as a library.The script constructs an isolated, local temporary
Contentrepository which its path is required when using demisto-sdk's relevant functionality.Currently the
CONTENT_PATHconstant is resolved statically (for obvious reasons) when importing the required modules, which prevents the script from utilizing it for validation and lint of the local temporary content repo.These changes expose an updating functionality for the global
CONTENT_PATHconstant and all of its derivations.