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

Docs: DevOps Pipelines #2252

Merged
merged 2 commits into from
Jun 7, 2023
Merged

Docs: DevOps Pipelines #2252

merged 2 commits into from
Jun 7, 2023

Conversation

joepavitt
Copy link
Contributor

@joepavitt joepavitt commented Jun 7, 2023

Description

  • Adds documentation for Staged Deployments/Pipelines
  • Adds "DevOps Pipeline" Concept description
  • Includes optimized images to support documentation

Related Issue(s)

Documentation for #2082

Checklist

@joepavitt joepavitt requested a review from knolleary June 7, 2023 13:48
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
Copy link
Contributor

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
Copy link
Contributor

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

@joepavitt joepavitt merged commit 98c4441 into main Jun 7, 2023
1 check passed
@joepavitt joepavitt deleted the docs-pipelines branch June 7, 2023 14:02
@joepavitt
Copy link
Contributor Author

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

@joepavitt
Copy link
Contributor Author

Have added the recommended changes here: #2254

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants