-
Notifications
You must be signed in to change notification settings - Fork 134
Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
- The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.
Description
For parity with the standard provider and the provider_meta schema slated to be added with #474, the user_agent schema should change to a list of strings in the v2.0.0 release. This is a breaking change, and unfortunately doesn't allow for migration prior to v2.0.0 as the argument name must be kept the same. We can potentially deprecate the existing argument, but a warning diagnostic when set might be more appropriate as the argument won't be removed.
We also might want to consider tackling hashicorp/aws-sdk-go-base#1397 as part of this change, given the current provider argument is the final upstream dependency relying on the UserAgentProduct data structure.
Potential Terraform Configuration
provider "awscc" {
user_agent = [
"example-module/1.0",
"BuildID/1234",
]
}References
Relates #474 (comment)
Relates hashicorp/terraform-provider-aws#45464
Relates hashicorp/aws-sdk-go-base#1397