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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hcp_vault_secrets_integration_aws doesn't require audience from the UI #1117

Open
jmeisele opened this issue Oct 15, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@jmeisele
Copy link

Terraform Version and Provider Version

Terraform version: 1.9.7
HCP provider version: 0.97.0

Affected Resource(s)

  • hcp_vault_secrets_integration_aws

Terraform Configuration Files

resource "hcp_vault_secrets_integration_aws" "this" {
  name         = "aws-secrets-manager"
  capabilities = ["DYNAMIC", "ROTATION"]
  federated_workload_identity = {
    role_arn = aws_iam_role.hashicorp_vault_secrets_role.arn
  }
  project_id = var.project_id
}

Debug Output

Panic Output

Steps to Reproduce

  1. terraform apply

Expected Behavior

Expect to supply just an IAM role to be assumed by AWS Secrets Manager integration like the docs read

Actual Behavior

audience argument is required in federated_workload_identity block

Important Factoids

References

https://developer.hashicorp.com/hcp/docs/vault-secrets/integrations/aws-secrets-manager
Confirmed working as written in the docs from the UI, only a role provided

  • #0000

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@jmeisele jmeisele added the bug Something isn't working label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant