-
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
Reflect protocol v6 changes in schema JSON output #28050
Comments
ack thank you radek that got lost in the shuffle ❤️ |
Aside: Can/should we bump the version?
I know these changes are not necessarily required but eventually downstream tooling (e.g. |
That is an excellent point @bflad , we've made a lot of additive changes and I have been neglecting that format version. I'll open a PR and make sure I ping our consumers. thanks for the nudge! |
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. |
Recent changes in #27699 and #27793 introduced some new fields for an attribute, which should probably be reflected somehow in the schema JSON output produced by
terraform providers schema -json
.The SDK doesn't seem to support v6 yet, so this currently has no real impact on end-users AFAICT, but when I tried adding some of the new fields to the builtin provider I saw a crash.
Terraform Version
Modified version of
e5538693ced0dc42bb90a3919875cb8bbd625736
(latest revision)Modified schema
terraform/builtin/providers/terraform/data_source_state.go
Lines 59 to 76 in 59b71de
(feel free to checkout
json-schema-export-crash
branch)Terraform Configuration Files
Crash Output
Expected Behavior
Output JSON schema
Actual Behavior
Crash
Steps to Reproduce
terraform init
terraform providers schema -json
The text was updated successfully, but these errors were encountered: