Skip to content
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

tfprotov6: Upgrade to Protocol Version 6.2 #143

Merged
merged 1 commit into from
Jan 20, 2022
Merged

Conversation

bflad
Copy link
Contributor

@bflad bflad commented Jan 20, 2022

Closes #142

Updated via:

pushd tfprotov6/internal/tfplugin6
./generate.sh
popd

Terraform Plugin Protocol version 6.1 includes a deprecation of the SchemaObject max_items and min_items fields. While this package could transitively also deprecate the fields in its exported types, this opts to instead remove them completely since they never worked as intended.

Terraform Plugin Protocol version 6.2 includes the ApplyResourceChange.Response and PlanResourceChange.Response message legacy_type_system field that was unintentionally missing from earlier versions. The tfprotov6 types errantly already included the UnsafeToUseLegacyTypeSystem fields (copied from tfprotov5), which were never wired through the protocol because the protocol did not implement them. That field is now passed through the protocol in both directions.

Reference: #142

Updated via:

```shell
pushd tfprotov6/internal/tfplugin6
./generate.sh
popd
```

Terraform Plugin Protocol version 6.1 includes a deprecation of the `SchemaObject` `max_items` and `min_items` fields. While this package could transitively also deprecate the fields in its exported types, this opts to instead remove them completely since they never worked as intended.

Terraform Plugin Protocol version 6.2 includes the `ApplyResourceChange.Response` and `PlanResourceChange.Response` message `legacy_type_system` field that was unintentionally missing from earlier versions. The `tfprotov6` types errantly already included the `UnsafeToUseLegacyTypeSystem` fields (copied from `tfprotov5`), which were never wired through the protocol because the protocol did not implement them. That field is now passed through the protocol in both directions.
@bflad bflad added bug Something isn't working breaking-change This will impact or improve our compatibility posture labels Jan 20, 2022
@bflad bflad added this to the v0.7.0 milestone Jan 20, 2022
@bflad bflad requested a review from a team January 20, 2022 16:38
@bflad bflad merged commit 60a8577 into main Jan 20, 2022
@bflad bflad deleted the bflad-tfprotov6-6.2 branch January 20, 2022 18:18
bflad added a commit that referenced this pull request Jan 20, 2022
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
breaking-change This will impact or improve our compatibility posture bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tfprotov6: Upgrade to Protocol Version 6.2
2 participants