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
Currently, when creating or updating an API token in the Rollbar UI, the scopes are now being ordered differently by default. For instance, the order is now "write, read" instead of the previous "read, write."
If any changes are made through the UI and we then apply Rollbar updates to the project, the planning phase fails. It seems that Terraform detects the change in scope order and attempts to recreate the token, which results in unauthorized errors . We attempted to adjust the scope order in our Terraform repository, but this caused similar issues with other Rollbar projects.
The text was updated successfully, but these errors were encountered:
Currently, when creating or updating an API token in the Rollbar UI, the scopes are now being ordered differently by default. For instance, the order is now "write, read" instead of the previous "read, write."
If any changes are made through the UI and we then apply Rollbar updates to the project, the planning phase fails. It seems that Terraform detects the change in scope order and attempts to recreate the token, which results in unauthorized errors . We attempted to adjust the scope order in our Terraform repository, but this caused similar issues with other Rollbar projects.
The text was updated successfully, but these errors were encountered: