-
Notifications
You must be signed in to change notification settings - Fork 11
vpc_firewall_rules: fix provider produced invalid plan #456
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
Conversation
5fc347c to
3de3991
Compare
|
3de3991 to
5ada4fc
Compare
karencfv
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for tackling this! Looks good.
Could you add an entry to the changelog for a breaking change since we're changing the schema?
3335ef6 to
b28af6f
Compare
|
Changelog added and tests are passing. |
karencfv
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing my comments! Sorry, I just realised we need to update the resource's documentation as well with the schema changes https://github.com/oxidecomputer/terraform-provider-oxide/blob/main/docs/resources/oxide_vpc_firewall_rules.md
b28af6f to
59b8ad3
Compare
No worries! I forgot too. Heat wave is making my brain melt this week haha. |
Added acceptance tests to surface the issue reported in #453. See #453 (comment) for an understanding of what's happening. Removed the computed attributes from the firewall rules since those computed fields were being updated for all of the rules, even when Terraform did not expect a rule to be updated. Unfortunately all of the computed attributes had to be removed for this to work and keep the update in-place logic.
59b8ad3 to
89c1622
Compare
karencfv
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Thanks for the fix!
Added acceptance tests to surface the issue reported in #453.
See #453 (comment) for an understanding of what's happening.
Removed the computed attributes from the firewall rules since those computed fields were being updated for all of the rules, even when Terraform did not expect a rule to be updated. Unfortunately all of the computed attributes had to be removed for this to work and keep the update in-place logic.