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.
Terraform CLI and Terraform AWS Cloud Control Provider Version
When we set theme_arn for aws_quicksight_analysis we expect it to be forwarded to the API call to create/update the analysis and applied to the analysis in Quicksight.
Actual Behavior
Instead of forwarding it to the API call it seems to set it back to null, so it is always reset to the default classic theme on every deployment.
We have tried to set it both to arn:aws:quicksight::aws:theme/MIDNIGHT and created a new theme with aws_quicksight_theme and linked to that.
I checked the source code for the resource for create and update and they do not include the themeArn as they should based on the GO API docs
Set theme_arn for a aws_quicksight_analysis to any other value than the classic theme, for example arn:aws:quicksight::aws:theme/MIDNIGHT, and verify that it is not applied.
Based on the source code it seems like aws_quicksight_dashboard has the same bug
Community Note
Terraform CLI and Terraform AWS Cloud Control Provider Version
Terraform v1.4.6 on darwin_arm64
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
None
Expected Behavior
When we set
theme_arn
foraws_quicksight_analysis
we expect it to be forwarded to the API call to create/update the analysis and applied to the analysis in Quicksight.Actual Behavior
Instead of forwarding it to the API call it seems to set it back to null, so it is always reset to the default classic theme on every deployment.
We have tried to set it both to
arn:aws:quicksight::aws:theme/MIDNIGHT
and created a new theme withaws_quicksight_theme
and linked to that.I checked the source code for the resource for create and update and they do not include the
themeArn
as they should based on the GO API docsCreateAnalysisInput and Update
Steps to Reproduce
Set
theme_arn
for aaws_quicksight_analysis
to any other value than the classic theme, for examplearn:aws:quicksight::aws:theme/MIDNIGHT
, and verify that it is not applied.Based on the source code it seems like
aws_quicksight_dashboard
has the same bug