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

Don't completely drop changes that have bad mappings #295

Merged
merged 2 commits into from
May 14, 2024

Conversation

dylanratcliffe
Copy link
Member

Fixes #284

I've done a bit of cleanup in this PR also and added some test data but the actual fix is the plannedChangeGroupsVar.Add change. We now have a failing test for this also

@dylanratcliffe dylanratcliffe requested a review from DavidS-ovm May 10, 2024 17:25
Copy link
Contributor

@DavidS-ovm DavidS-ovm left a comment

Choose a reason for hiding this comment

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

One minor nit about improving the log message (see inline).

This code also could do with a general cleanup pass to move all the plan handling stuff into a separate file, but not in this PR

cmd/terraform_plan.go Outdated Show resolved Hide resolved
Co-authored-by: David Schmitt <[email protected]>
@dylanratcliffe dylanratcliffe enabled auto-merge May 14, 2024 11:24
@dylanratcliffe dylanratcliffe merged commit 486c518 into main May 14, 2024
5 checks passed
@dylanratcliffe dylanratcliffe deleted the stop-droppping-unmapped branch May 14, 2024 11:27
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.

Mapping problem for modules with count
2 participants