Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add rulesets instance key #803

Closed
cognifloyd opened this issue May 9, 2023 · 1 comment
Closed

Add rulesets instance key #803

cognifloyd opened this issue May 9, 2023 · 1 comment
Assignees
Labels
area/server Indicates a change to the server feature Indicates a new feature

Comments

@cognifloyd
Copy link
Member

Description

Add a new instance key under step rulesets. This allows a pipeline to skip steps if the pipeline is running on an unexpected vela instance.

Today, we can check VELA_ADDR in step commands to opt-in/out on certain instances. A ruleset that can completely remove irrelevant steps during pipeline compilation would be much better.

Value

I need a Vela instance in the EU, and a different one in the US. Both instances process some of the same repos. Some steps should only run in EU or in US.

I also have seperate dev/prod Vela clusters. Some steps might only apply to one or the other.

Definition of Done

Add new instance yaml key under step.rulesets that allows steps to run only on particular cluster(s).

The instance check happens during pipeline compilation to remove irrelevant steps.

Effort (Optional)

unknown

Impacted Personas (Optional)

Users that need to distinguish between multiple Vela instances.

@cognifloyd cognifloyd added the feature Indicates a new feature label May 9, 2023
@wass3rw3rk wass3rw3rk added the area/server Indicates a change to the server label May 11, 2023
@wsan3 wsan3 self-assigned this Jul 9, 2024
@wass3rw3rk
Copy link
Member

this should be in the next version - thanks for the idea ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/server Indicates a change to the server feature Indicates a new feature
Projects
None yet
Development

No branches or pull requests

3 participants