feat: add github_actions_runner_group_repository_access resource#3376
Open
BronzeDeer wants to merge 1 commit intointegrations:mainfrom
Open
feat: add github_actions_runner_group_repository_access resource#3376BronzeDeer wants to merge 1 commit intointegrations:mainfrom
BronzeDeer wants to merge 1 commit intointegrations:mainfrom
Conversation
Resolves integrations#3375 Currently the only way to control which repositories have access to a specific runner group is via the central runner group resource `github_actions_runner_group`, which manages the list of all repositories that have access to the runner group. In many cases, especially surrounding building Internal Development Platforms which create managed repositories as needed it is not desirable to centralize the list of repositories in a central state and rather allow independent, potentially concurrent deployment processes to add/remove a specific repository. This commit adds a new resource which allows to configure this access on a single repo basis without needing to track the state of all authorized repositories for a runner group
|
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
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.
Resolves #3375
Currently the only way to control which repositories have access to a specific runner group is via the central runner group resource
github_actions_runner_group, which manages the list of all repositories that have access to the runner group. In many cases, especially surrounding building Internal Development Platforms which create managed repositories as needed it is not desirable to centralize the list of repositories in a central state and rather allow independent, potentially concurrent deployment processes to add/remove a specific repository.This commit adds a new resource which allows to configure this access on a single repo basis without needing to track the state of all authorized repositories for a runner group
Before the change?
After the change?
Pull request checklist
Does this introduce a breaking change?