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

Figure out plugin protocol versioning evolution #120

Open
f0rmiga opened this issue Jan 20, 2022 · 1 comment
Open

Figure out plugin protocol versioning evolution #120

f0rmiga opened this issue Jan 20, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@f0rmiga
Copy link
Contributor

f0rmiga commented Jan 20, 2022

Right now, we don't test or support older protocol versions. We need to come up with a better story for this. Perhaps the SDK could do some work when a plugin is too old and doesn't support a specific method? This task is broad and the outcome should be a small design doc with some POC.

@f0rmiga f0rmiga added this to the 1.0 milestone Jan 20, 2022
@mattem mattem added the enhancement New feature or request label Mar 21, 2022
@alexeagle
Copy link
Member

Note that terraform has an extensive doc on versioning: https://github.com/hashicorp/terraform/tree/main/docs/plugin-protocol

I'd strongly prefer that we follow that as much as possible - part of our decision to use the hashicorp go-plugin system was that this is a solved problem.

@cgrindel cgrindel removed this from the CLI MVP - Release 1.0.0 milestone Oct 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

4 participants