This repository was archived by the owner on Jul 22, 2025. It is now read-only.
fix: granted space permissions forcing UI order #862
Merged
Conversation
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
denys-octopus
approved these changes
Feb 9, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
fixes #539
I could not get this resource to migrate to framework while maintain backwards compatibility. In addition because of the way our API works a resource like this would not work well in framework. This is because if the granted space permission are invalid instead of throwing an error the API would automatically include the "missing" permission causing terraform plugin framework to always complain the plan does not match the outcome.
This is a fix stop reordering in SDK, in the future we can consider a new resource framework that would not need to carry over the legacy of this resource. Creating the new resource now would have little benefit over this fix.
Despite the schema changes, no migration is needed.