feat: add data sources github_actions_remove_token and github_actions_organization_remove_token #2702
Conversation
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
Add github_actions_remove_token data source to retrieve remove tokens for GitHub Actions runners. The data source provides token and expiration time fields for managing runner removal operations.
…st repositories to avoid drift, as vuln alerts are automatically activated for newly created repositories
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #2696
Before the change?
github_actions_remove_tokendidn't existgithub_actions_organization_remove_tokendidn't existgithub_actions_registration_tokendoes not work, because for new repo creationvulnerability_alertsis automatically activated, which is not reflected in tests, leading to immediate driftAfter the change?
github_actions_remove_tokenlets you create a self-hosted runner remove token at the repository levelgithub_actions_organization_remove_tokenlets you create a self-hosted runner remove token at the organization levelgithub_actions_remove_tokenandgithub_actions_organization_remove_tokensimilar to tests forgithub_actions_registration_tokenandgithub_actions_organization_registration_tokengithub_actions_registration_token, by registering of test repo with activated vulnerability alertsgithub_actions_registration_tokenandgithub_actions_organization_registration_tokenPull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!