provider: Migrate to standalone plugin SDK v1.1.1 #108
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.
This also introduces change in how the provider reports itself via
User-Agent
header.I went ahead and used the SDK's helper
httpclient.TerraformUserAgent
function, assuming that you would prefer UA string which looks more RFC-compliant and uses spaces as separators, instead of semicolons. I am however open to retain backwards compatibility and modify that part of the PR, should it block merging.Migrating to the standalone SDK is IMO much higher priority than cleaning up technical debt.
I did not run any acceptance tests (yet).