-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
command/jsonprovider: bump format version #28115
Conversation
Support for attributes with NestedTypes was added in #28055, and should have included a format version bump: this is a backwards-compatible change, but consumers will need to be updated in order to properly decode attributes (with NestedTypes) going forward.
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.
LGTM, I already have a draft PR, so I'll just reflect this version change there.
I reckon instead of string-matching the version we'll need to start parsing it as semver and check if it's =<
than supported (0.2) and then continue erroring in the unmarshaller if it's not. Alternatively we can continue exact-matching it and have a slice of two strings. 🤷🏻♂️
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.
Seeing as this is just a version bump, 👍 here too.
We'll look at the implications of this over in terraform-json.
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.
Thank you so much!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Support for attributes with NestedTypes was added in #28055, and that PR should have included a format version bump: this is a backwards-compatible change, but consumers will need to be updated in order to properly decode attributes (with NestedTypes) going forward.
Thanks @bflad for the nudge!
@vancluever , I am sorry I did not include you on the last PR (#28055); if you have questions / see any problems / have any requests I'll get right on 'em.