-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Bug] Temporal Cloud User with no namespace access #115
Labels
bug
Something isn't working
Comments
DmytroRomantsovM
changed the title
[Bug] FILL_TITLE_HERE
[Bug] Temporal Cloud User with no namespace access
Aug 14, 2024
Another approach is to specify all namespaces, which also gives an error: Terraform plan:
Terraform apply:
|
swgillespie
added a commit
that referenced
this issue
Sep 24, 2024
This PR addresses #119, #116, and #115 by decoupling the definition of user accesses from the user itself, via a new resource: `temporalcloud_user_namespace_access`. This resource is intended to provide a many-to-many mapping between namespaces and users. Under the hood, this resource is manipulating a single User object via the API (as the underlying data model stashes all namespaces accesses on the user object), while also preserving the invariant that adding or removing a single user from a single namespace won't obliterate the list of permissions that a user has. I do intend to write some more tests but I wanted to get this out quickly for review for some fast feedback before I write a bunch of tests that exercise things that might change in review.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What are you really trying to do?
Create a Temporal Cloud User with no namespace access and
read
account access.Describe the bug
Terrafrom returned the following error:
temporalcloud_user.user: Creating...
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to temporalcloud_user.user, provider
│ "provider["registry.terraform.io/temporalio/temporalcloud"]" produced an
│ unexpected new value: .namespace_accesses: was
│ cty.ListValEmpty(cty.Object(map[string]cty.Type{"namespace_id":cty.String,
│ "permission":cty.String})), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
Minimal Reproduction
For example:
resource "temporalcloud_user" "user" {
account_access = "read"
email = "[email protected]"
namespace_accesses = []
}
Environment/Versions
The text was updated successfully, but these errors were encountered: