Open
Conversation
Author
|
@kaganatlassian2 could you please review this PR? |
kaganatlassian2
pushed a commit
that referenced
this pull request
Feb 6, 2026
Fixed an issue where the api_key value was being removed from the state file (where it was previously present) after consecutive terraform apply runs. Approved-by: Bekir Kağan Yıldız
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR introduces a new Terraform resource atlassian-operations_team_role that enables management of team roles in Atlassian JSM Operations. Team roles provide granular permission control for team members, allowing administrators to define specific access rights and restrictions.
Note: Currently there is no API available to assign team members the team role. See open feature request https://jira.atlassian.com/browse/JSDCLOUD-17225