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

pingone_gateway_role_assignment: Intermittent attribute 'read_only' expected "false", got "true" #130

Closed
patrickcping opened this issue Sep 11, 2022 · 1 comment
Labels
service/base PingOne Platform status/blocked/upstream-api The issue/PR is blocked by an upstream API

Comments

@patrickcping
Copy link
Collaborator

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

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

PingOne Terraform provider Version

v0.4.0

Terraform Version

N/a

Affected Resource(s)

  • pingone_gateway_role_assignment

Terraform Configuration Files

# Copy-paste your PingOne related Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

# Remember to replace any account/customer sensitive information in the configuration before submitting the issue
data "pingone_environment" "general_test" {
  name = "tf-testacc-general-test"
}

resource "pingone_environment" "abc" {
  name = "tf-testacc-abc"
  type = "SANDBOX"
  license_id = var.license_id
  default_population {
  }
  service {
  }
}

resource "pingone_gateway" "def" {
  environment_id = data.pingone_environment.general_test.id
  name           = "def"
  enabled        = true

  type = "PING_FEDERATE"
}

data "pingone_role" "def" {
  name = "Identity Data Admin"
}

resource "pingone_gateway_role_assignment" "def" {
  environment_id = data.pingone_environment.general_test.id
  gateway_id     = pingone_gateway.def.id
  role_id        = data.pingone_role.def.id

  scope_environment_id = pingone_environment.abc.id
}

Debug Output

Output from acceptance test:

=== CONT  TestAccRoleAssignmentGateway_Environment
    resource_gateway_role_assignment_test.go:118: Step 1/3 error: Check failed: Check 8/8 error: pingone_gateway_role_assignment.esbsuvzrwz: Attribute 'read_only' expected "false", got "true"
    testing_new.go:84: Error running post-test destroy, there may be dangling resources: exit status 1
        
        Error: Role assignment *** cannot be deleted as it is read only

Panic Output

Expected Behavior

Role assignment created and API responds with read_only value of false, role assignment can be subsequently destroyed.

Actual Behavior

Rarely, the role assignment is created and API responds with read_only value of true. The role cannot be removed and the destroy fails.

Steps to Reproduce

  1. terraform apply

Important Factoids

References

@patrickcping patrickcping added question Further information is requested service/base PingOne Platform labels Sep 11, 2022
@patrickcping patrickcping added status/blocked/upstream-api The issue/PR is blocked by an upstream API and removed question Further information is requested labels Sep 29, 2022
@patrickcping
Copy link
Collaborator Author

patrickcping commented Mar 17, 2023

This issue hasn't been observed in the automated tests for several months - closing the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/base PingOne Platform status/blocked/upstream-api The issue/PR is blocked by an upstream API
Projects
None yet
Development

No branches or pull requests

1 participant