Conversation
gridscale_loadbalancer.status is server-derived (only ever set via d.Set from the API response, never read from user config in Create/Update). Declaring it Optional with Default "active" causes a perpetual plan diff whenever the server reports a status other than "active". Mark it Computed and drop the Default.
fabiante
approved these changes
Jul 17, 2026
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
2 participants
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.
Problem
gridscale_loadbalancer.statusis server-derived — it is only ever set viad.Setfrom the API response and never read from user config in Create/Update. Declaring itOptionalwithDefault: "active"produces a perpetual plan diff whenever the load balancer reports a status other thanactive. It is also the only resource whosestatusis Optional rather than Computed.Fix
Mark
statusasComputed: trueand drop theDefault, matching the other resources.