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.

Sign up for GitHub

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

fix: indentation on deploytarget docs #3167

Merged
merged 2 commits into from
Jun 2, 2022
Merged

fix: indentation on deploytarget docs #3167

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4a0a59d
fix: indentation on deploytarget docs
shreddedbacon Jun 2, 2022
73799b6
Merge branch 'main' into docs-deploytarget-fix
tobybellwood Jun 2, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions docs/using-lagoon-advanced/deploytarget-configs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,23 +16,23 @@ The basic idea of a DeployTarget configuration is that it is a way to easily def
Before going in to how to configure a project to leverage DeployTarget configurations, there are some things you need to know.

1. Environments now have two new fields available to them to identify which DeployTarget(Openshift or Kubernetes) they have been created on.
1. openshiftProjectPattern
2. openshift
1. openshiftProjectPattern
2. openshift
2. Once an environment has been deployed to a specific DeployTarget, it will always deploy to this target, even if the DeployTarget configuration, or project configuration is modified.
1. This offers some safety to existing environments by preventing changes to DeployTarget configurations from creating new environments on different clusters.
2. This is a new feature that is part of Lagoon, not specifically for DeployTarget configurations.
1. This offers some safety to existing environments by preventing changes to DeployTarget configurations from creating new environments on different clusters.
2. This is a new feature that is part of Lagoon, not specifically for DeployTarget configurations.
3. By default, if no DeployTarget configurations are associated to a project, that project will continue to use the existing methods to determine which environments to deploy. These are the following fields used for this.
1. branches
2. pullrequests
3. openshiftProjectPattern
4. openshift
1. branches
2. pullrequests
3. openshiftProjectPattern
4. openshift
4. As soon as any DeployTarget configurations are added to a project, then all future deployments for this project will use these configurations. What is defined in the project is ignored, and overwritten to inform users that DeployTarget configurations are in use.
5. DeployTarget configurations are weighted, which means that a DeployTarget configuration with a larger weight is prioritised over one with lower weight.
1. The order in which they are returned by the query is the order they are used to determine where an environment should be deployed.
1. The order in which they are returned by the query is the order they are used to determine where an environment should be deployed.
6. Active/Standby environments can only be deployed to the same cluster, so your DeployTarget configuration must be able to deploy both those environments to the same target.
7. Projects that leverage the `promote` feature of Lagoon must be aware that DeployTarget configurations are ignored for the `destination` environment.
1. The destination environment will always be deployed to the same target that the `source` environment is on, your DeployTarget configuration MUST be configured correctly for this `source` environment.
2. For safety, it is best to define both the `source` and `destination` environment in the same DeployTarget configuration branch regex.
1. The destination environment will always be deployed to the same target that the `source` environment is on, your DeployTarget configuration MUST be configured correctly for this `source` environment.
2. For safety, it is best to define both the `source` and `destination` environment in the same DeployTarget configuration branch regex.

## Configuration

Expand Down