Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws_emr_cluster configurations_json hue-ini.bind_password stored as *******? #20611

Open
marekaf opened this issue Aug 18, 2021 · 2 comments
Open
Labels
bug Addresses a defect in current functionality. service/emr Issues and PRs that pertain to the emr service.

Comments

@marekaf
Copy link

marekaf commented Aug 18, 2021

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

Terraform CLI and Terraform AWS Provider Version

Terraform v1.0.1
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v3.39.0
+ provider registry.terraform.io/hashicorp/null v3.1.0
+ provider registry.terraform.io/hashicorp/random v3.1.0

Affected Resource(s)

  • aws_emr_cluster

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

      {
        "Classification" : "hue-ini",
        "Properties" : {},
        "Configurations" : [
          {
            "Classification" : "desktop",
            "Properties" : {},
            "Configurations" : [
              {
                "Classification" : "ldap",
                "Properties" : {},
                "Configurations" : [
                  {
                    "Classification" : "ldap_servers",
                    "Properties" : {},
                    "Configurations" : [
                      {
                        "Classification" : "xyz",
                        "Properties" : {
                          "search_bind_authentication" : "true",
                          "base_dn" : "ou=acme,dc=acme,dc=local",
                          "ldap_username_pattern" : "CN=<username>,OU=acme Project,OU=Users,OU=acme,DC=acme,DC=local",
                          "ldap_url" : "ldap://someldap.org:389",
                          "bind_dn" : "CN=acme,OU=acme,OU=Users,DC=acme,DC=local",
                          "bind_password" : "${var.bind_password}"
                        }
                      }
                    ]
                  }
                ]
              },
              {
                "Classification" : "auth",
                "Properties" : {
                  "backend" : "desktop.auth.backend.LdapBackend"
                }
              }
            ]
          },
          {
            "Classification" : "beeswax",
            "Properties" : {
              "download_row_limit" : "1000000"
            }
          }
        ]
      },


  // triggers a change for this every time
  bind_password = jsondecode(data.aws_secretsmanager_secret_version.ldap.secret_string)["password"]

  //bind_password = sensitive("********")

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

Steps to Reproduce

  1. terraform apply

Important Factoids

References

@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. service/emr Issues and PRs that pertain to the emr service. labels Aug 18, 2021
@ewbankkit ewbankkit added bug Addresses a defect in current functionality. and removed needs-triage Waiting for first response or review from a maintainer. labels Aug 20, 2021
@foxlzl
Copy link

foxlzl commented May 19, 2023

Any update on this bug? It's still there and causing forced cluster redeployment.

@ewbankkit
Copy link
Contributor

Relates #12683.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Addresses a defect in current functionality. service/emr Issues and PRs that pertain to the emr service.
Projects
None yet
Development

No branches or pull requests

3 participants