You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
│ Error: Error: API responded with a 401 Unauthorized
│
│ with rabbitmq_federation_upstream.this,
│ on federation.tf line 17, in resource "rabbitmq_federation_upstream" "this":
│ 17: resource "rabbitmq_federation_upstream" "this" {
Expected Behavior
I should be able to re-appy or delete at any point in time.
Actual Behavior
I get a 401 Unauthorized for every operation after the initial resource creation.
Steps to Reproduce
Run terraform apply
Run terraform apply again
Important Factoids
This happens at a regular CloudAMQP managed cluster.
Running a curl to read the resource manually works: curl -XGET -u {redacted}:{redacted} https://{redacted}/api/parameters/federation-upstream/dev/test
References
n/a
The text was updated successfully, but these errors were encountered:
zeebonk
changed the title
Unable plan/destroy an initially succesufully created federation upstream
Unable plan/destroy an initially succesfully created federation upstream
Mar 8, 2022
zeebonk
changed the title
Unable plan/destroy an initially succesfully created federation upstream
Unable plan/destroy an initially sccesfully created federation upstream
Mar 8, 2022
zeebonk
changed the title
Unable plan/destroy an initially sccesfully created federation upstream
Unable plan/destroy an initially succesfully created federation upstream
Mar 8, 2022
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
I should be able to re-appy or delete at any point in time.
Actual Behavior
I get a 401 Unauthorized for every operation after the initial resource creation.
Steps to Reproduce
terraform apply
terraform apply
againImportant Factoids
curl -XGET -u {redacted}:{redacted} https://{redacted}/api/parameters/federation-upstream/dev/test
References
n/a
The text was updated successfully, but these errors were encountered: