-
Notifications
You must be signed in to change notification settings - Fork 156
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
Feature Request: "custom stage” mechanism #1089
Labels
Comments
@ShotaKitazawa Thank you for raising the issue. This is definitely a worthwhile feature. We will add it to the roadmap. |
We are thinking about adding a |
This was referenced Feb 20, 2023
Merged
Merged
This was referenced Mar 2, 2023
I think we have three ways to use custom stage.
pipeline:
stages:
- name: CUSTOM_SYNC
with:
runs:
- "sam build"
- "echo y | sam deploy"
pipeline:
stages:
- name: CUSTOM_CANARY
with:
runs:
- "sam build"
- "echo y | sam deploy"
- name: CUSTOM_CANARY_PROMOTE
desc: "50%"
with:
runs:
- "echo y | sam deploy --parameter-overrides FUNCTION_WAIT=0.5"
- name: WAIT
with:
duration: 1m
- name: CUSTOM_CANARY_PROMOTE
desc: "100%"
with:
runs:
- "echo y | sam deploy --parameter-overrides FUNCTION_WAIT=1"
pipeline:
stages:
- name: K8S_CANARY_ROLLOUT
with:
replicas: 10%
- name: COMMAND_EXEC
desc: "webhook"
with:
runs:
- "curl https://hooks.slack.com/services"
- name: WAIT
with:
duration: 10s
- name: K8S_PRIMARY_ROLLOUT
- name: K8S_CANARY_CLEAN |
This was referenced Mar 23, 2023
This feature will be released in v0.44.0 for only AWS Lambda. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added:
"custom stage” mechanism (e.g. https://spinnaker.io/guides/operator/custom-job-stages/)
Why is this needed:
Now, PipeCD support some stages.
(eg. Kubernetes: https://pipecd.dev/docs/user-guide/configuring-deployment/kubernetes/)
But I want to execute some processes (eg. Run fixed K8s Job) only writing in .pipe.yaml
I hope feature of custom (user-definition) stage.
The text was updated successfully, but these errors were encountered: