Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a test showing bug in merge if variables are used for keys #2101

Merged
merged 1 commit into from
Jan 9, 2025

Conversation

denik
Copy link
Contributor

@denik denik commented Jan 8, 2025

Since merge happens first, before variable resolution, the two jobs are seen as different.

I also updated override/job_cluster/script to include more of the output.

Since merge happens first, before variable resolution, two jobs are seen as different.
Copy link
Contributor

@pietern pietern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we can safely move the merge mutators to run after variable interpolation.

@denik denik added this pull request to the merge queue Jan 9, 2025
Merged via the queue into main with commit 2a4fdd9 Jan 9, 2025
9 checks passed
@denik denik deleted the denik/job_cluster_var branch January 9, 2025 10:21
github-merge-queue bot pushed a commit that referenced this pull request Jan 13, 2025
## Changes
Move mutator.Merge{JobClusters,JobParameters,JobTasks,PipelineClusters}
after variable resolution. This helps with the case when key contains a
variable.

@pietern mentioned here
#2101 (review)
it should be safe.

## Tests
Existing acceptance that was capturing the bug is updated with corrected
output.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants