Remove extra_data from SNow CVE Remediation workflow nodes#127
Merged
Conversation
…gate Jinja2 in extra_data is evaluated at CaC load time where host_fqdn and reported_cve are undefined, storing empty strings that shadow the actual workflow launch vars. Since both JTs have ask_variables_on_launch: true, the workflow-level extra_vars propagate automatically. Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Jinja2 in workflow node extra_data resolves at CaC load time (empty) not at runtime. Remove it — workflow-level extra_vars propagate automatically via ask_variables_on_launch.