Backport of CI: Dynamic runs-on values for oss/ent into release/1.3.x #17817
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.
Backport
This PR is auto-generated from #17775 to be assessed for backporting due to the inclusion of the label backport/1.3.x.
The below text is copied from the body of the original PR.
In order to fetch secrets from Vault in our Enterprise repo, we need to use self-hosted runners, but here in this public repo, we may only use public runners.
To reduce merge conflicts between OSS and ENT (and backports..), this PR adds conditions that will result in public runners here in OSS, but self-hosted runners in ENT. I have done a lot of trial-and-error to end up with what I hope is a nice middle-ground between complexity, explicitness, and non-mergeflictery.
A subsequent PR will add the steps to (again, conditionally) fetch secrets from Vault.