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
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
if I set to password to ******** it says no changes.
it seems like the password is internally (either in AWS provider or actually in EMR API) represented as those asterisks
Debug Output
Panic Output
Expected Behavior
No changes. Your infrastructure matches the configuration.
Actual Behavior
# module.emr.aws_emr_cluster.main[0] must be replaced
-/+ resource "aws_emr_cluster" "main" {
~ arn = "arn:aws:elasticmapreduce:eu-central-1:xyz:cluster/j-2M327SQ49FS10" -> (known after apply)
~ cluster_state = "WAITING" -> (known after apply)
~ configurations_json = (sensitive) # forces replacement
Community Note
Terraform CLI and Terraform AWS Provider Version
Affected Resource(s)
Terraform Configuration Files
Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.
if I set to password to
********
it says no changes. it seems like the password is internally (either in AWS provider or actually in EMR API) represented as those asterisksDebug Output
Panic Output
Expected Behavior
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
References