"aws_quicksight_user" resource doesn't allow custom namespace

[YuriGal]

Terraform CLI and Terraform AWS Provider Version

Terraform v1.0.8
on darwin_amd64
provider registry.terraform.io/hashicorp/aws v3.60.0

Affected Resource(s)

• aws_quicksight_user

Terraform Configuration Files

resource "aws_quicksight_user" "author" {
  email         = "email@example.com"
  identity_type = "IAM"
  user_role     = "AUTHOR"
  iam_arn       = aws_iam_user.user.arn
  namespace     = "NewOrg"
  provider      = aws.us-east-1
}

Expected Behavior

User should be created in the namespace "NewOrg"

Actual Behavior

Error message: "expected namespace to be one of [default], got NewOrg"

Steps to Reproduce

Just try to create a quicksight user in any namespace besides default.

AWS API (i.e. CLI aws quicksight register-user --namespace) does support registering user in a different namespace. Could you make this available in the provider as well?

[justinretzolk]

Hey @YuriGal 👋 Thank you for taking the time to file this issue. I took a look over the relevant CLI, API, and Go SDK documents for this, and it looks like this is a limitation of the underlying API. In each of the linked documents, it has a similar note for namespace:

The namespace. Currently, you should set this to default.

Since this is a limitation of the API, I'm going to close this issue for now. If this becomes available in the API at a later date, we can look into adding the functionality to the provider.

[YuriGal]

@justinretzolk thanks for getting back to me! I thought it was API limitation too (looking at these docs), but then I followed this guide in my research and it does use following CLI command:

aws quicksight register-user --aws-account-id $AAI --namespace Customer1 --identity-type IAM --iam-arn arn:aws:iam::$AAI:user/Customer1-Author1 --user-role AUTHOR --email Customer1-Author1@quicksightadminworkshop.com --region $IR

It uses custom namespace - and I tried it - and it does work.

[justinretzolk]

Hey @YuriGal; thanks so much for that update. With that in mind, I'm going to reopen this so that we can look into it a bit more when time permits.

[github-actions]

This functionality has been released in v4.6.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.