-
Notifications
You must be signed in to change notification settings - Fork 59
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
Docs: DevOps Pipelines #2252
Docs: DevOps Pipelines #2252
Conversation
The pipeline then allows you to move your full flow and configuration along from "Development" | ||
to "Production" once it's ready. | ||
|
||
In order to configure this in FlowForge, you can do this in your Application. Note you will need to have created |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds a bit clunky, but I can't place a finger on why.
Perhaps:
You can configure this in FlowForge from the Application screen.
Each stage currently is deployed manually. To do so, click the "play" icon on the source stage. In the example above, | ||
it will push from the "Development" stage to the "Production" stage. | ||
|
||
**Environment Variables** - When pushing to a next stage, only your environment variable keys |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the fact it's only KEYS should stand out more
that's annoying, apologies for merging before applying changes Pez. GitHub loaded with your approval, but didn't show any of the recommended changes, so I just merged, then just saw the emails |
Have added the recommended changes here: #2254 |
Description
Related Issue(s)
Documentation for #2082
Checklist