Vvasudevan process templates docs #2801
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
First pass of process templates docs
Co-authored-by: Steve Fenton <99181436+steve-fenton-octopus@users.noreply.github.com>
Co-authored-by: Steve Fenton <99181436+steve-fenton-octopus@users.noreply.github.com>
Co-authored-by: Steve Fenton <99181436+steve-fenton-octopus@users.noreply.github.com>
Co-authored-by: Steve Fenton <99181436+steve-fenton-octopus@users.noreply.github.com>
Co-authored-by: Steve Fenton <99181436+steve-fenton-octopus@users.noreply.github.com>
Co-authored-by: Steve Fenton <99181436+steve-fenton-octopus@users.noreply.github.com>
There was a problem hiding this comment.
Minor nitpick. This screen says Add credentials to use in version-controlled projects. My understanding is that credentials referenced here can be used in projects that are database-backed too. Possibly the same text has been reused from the Library page?
src/pages/docs/platform-hub/index.md
Outdated
| You can create and manage your process templates and policies from Platform Hub. | ||
|
|
||
| - [Process templates](/docs/platform-hub/process-templates) are reusable sets of deployment steps that can be shared across multiple spaces in Octopus Deploy | ||
| - [Policies](/docs/platform-hub) in Octopus are designed to ensure compliance and governance by default, making it easier to enforce pre- and post-deployment controls at scale. |
There was a problem hiding this comment.
Suggested change
| - [Policies](/docs/platform-hub) in Octopus are designed to ensure compliance and governance by default, making it easier to enforce pre- and post-deployment controls at scale. | |
| - [Policies](/docs/platform-hub) in Octopus are designed to ensure compliance and governance by default, making enforcing pre- and post-deployment controls at scale easier. |
src/pages/docs/platform-hub/index.md
Outdated
|
|
||
| You can create and manage Git Credentials in Platform Hub by visiting the Git Credentials screen in the Platform Hub navigation menu. You can use Git Credentials inside your process templates by selecting them from a dropdown in the step field that requires them. | ||
|
|
||
| :::hint These are not the same Git credentials that are used to configure Platform Hub::: |
There was a problem hiding this comment.
Suggested change
| :::hint These are not the same Git credentials that are used to configure Platform Hub::: | |
| :::hint | |
| These are not the same Git credentials that are used to configure Platform Hub | |
| ::: |
|
|
||
| Process templates are reusable sets of deployment steps that can be shared across multiple spaces in Octopus Deploy. Instead of copying and pasting deployment processes across teams and applications, which often leads to configuration drift, unnecessary duplication, and operational debt, you create a single source of truth that any project can consume. By abstracting your best practices for deployments into Process Templates, you make it easy for teams to follow standards and accelerate delivery. | ||
|
|
||
| :::warning Process templates are in Public Preview for all Enterprise Cloud Customers::: |
There was a problem hiding this comment.
Suggested change
| :::warning Process templates are in Public Preview for all Enterprise Cloud Customers::: | |
| :::warning | |
| Process templates are in Public Preview for all Enterprise Cloud Customers. | |
| ::: |
|
|
||
| :::warning Process templates are in Public Preview for all Enterprise Cloud Customers::: | ||
|
|
||
| To create or manage your process templates, navigate to Platform Hub. If you haven't setup your Git repository, you must do so first before creating a process template. Similarly, If you've already created templates or are joining an existing team, you'll see the existing templates in the template overview screen. |
There was a problem hiding this comment.
Suggested change
| To create or manage your process templates, navigate to Platform Hub. If you haven't setup your Git repository, you must do so first before creating a process template. Similarly, If you've already created templates or are joining an existing team, you'll see the existing templates in the template overview screen. | |
| To create or manage your process templates, navigate to Platform Hub. If you haven't set up your Git repository, you must do so first before creating a process template. Similarly, if you've already created templates or are joining an existing team, you'll see the existing templates in the template overview screen. |
| 10. Add the Worker Pool parameter to the **Worker Pool** field. | ||
| 11. Paste the following PowerShell script into the **Inline Source Code** editor: | ||
|
|
||
| ```ps |
There was a problem hiding this comment.
Suggested change
| ```ps | |
| ```powershell |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed up spelling, consolidated pages and added images