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 Nov 30, 2021. It is now read-only.
In my quest to achieve pipelines in Deis, I've got 2x applications:
myproject
myproject-staging
Underneath the myproject-staging app I want a button: Promote to Production which when clicked will put the exact same image onto the production app (myproject).
It seems the way to get this working is to make an API call like:
The problem is that this only works for Docker image references and doesn't support passing in a slug built reference.
I'm not going to say buildpacks are a requirement for me right now, but it would allow me to implement pipelines for all application types.
The text was updated successfully, but these errors were encountered:
If the use case is just "promote to production" then that can be solved via deis pipeline:promote which is something that was proposed in deis/deis#1318. That use case shouldn't be too hard to create a new feature request for, since we're just "promoting" the staging app's latest build to become the production app's latest build.
In my quest to achieve pipelines in Deis, I've got 2x applications:
Underneath the
myproject-staging
app I want a button:Promote to Production
which when clicked will put the exact same image onto the production app (myproject).It seems the way to get this working is to make an API call like:
The problem is that this only works for Docker image references and doesn't support passing in a slug built reference.
I'm not going to say buildpacks are a requirement for me right now, but it would allow me to implement pipelines for all application types.
The text was updated successfully, but these errors were encountered: