feat: provider: add a specific User-Agent inside configuration of the terraform provider #45
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… terraform provider Goal is to be able to determine usage between people using terraform-provider-ovh directly or using it through Crossplane provider.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of your changes
Inject a fixed user-agent config inside the terraform provider config.
Goal is to be able to determine usage between people using terraform-provider-ovh directly or using it through Crossplane provider on OVHcloud side, to determine if the provider have a lot of usage or not.
How has this code been tested
I used "make local-deploy" and checked that the configuration was correctly applied inside the terraform-provider config.