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
{{ message }}
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
The user should be able to target runner profiles to specific remote runners, then configure projects and applications to use specific runner profiles.
@xiaolin-ninja really looking forward to this! Will it also be possible to configure env vars to be applied in the targetable runner? I use Nomad, but also have ACLs enabled, and I use Vault to create a Nomad ACL token with a short TTL to run my jobs and then expire. Passing a short-lived ACL token to the Nomad runner in the NOMAD_TOKEN env var would be great for keeping Nomad API access secure while also allowing Waypoint to do its job.
@xiaolin-ninja really looking forward to this! Will it also be possible to configure env vars to be applied in the targetable runner? I use Nomad, but also have ACLs enabled, and I use Vault to create a Nomad ACL token with a short TTL to run my jobs and then expire. Passing a short-lived ACL token to the Nomad runner in the NOMAD_TOKEN env var would be great for keeping Nomad API access secure while also allowing Waypoint to do its job.
Hi @paladin-devops, this is an interesting idea! Currently there's env var configuration for runners, but sounds like you're describing dynamic configurations, like we have for applications, but for runners? We definitely want to explore this further, could you please open a feature request with more details and examples?
RFC
The user should be able to target runner profiles to specific remote runners, then configure projects and applications to use specific runner profiles.
This is useful for multi-environment workflows.
The text was updated successfully, but these errors were encountered: