summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDylan Griffith <dyl.griffith@gmail.com>2018-03-28 17:46:52 +1100
committerDylan Griffith <dyl.griffith@gmail.com>2018-03-29 14:44:34 +1100
commit8f9b5455142408898670dabde85d1c5a2e77d920 (patch)
tree1f9eefee7c2e98f0b126fa8bdfde1c3006721df8
parent092445a4025bc1033e2028655ba739961f5e4ebb (diff)
downloadgitlab-ce-41436-use-simpler-env-vars-for-auto-devops-replicas.tar.gz
Correct documentation regarding track names and auto devops env vars (#41436)41436-use-simpler-env-vars-for-auto-devops-replicas
-rw-r--r--doc/topics/autodevops/index.md13
1 files changed, 6 insertions, 7 deletions
diff --git a/doc/topics/autodevops/index.md b/doc/topics/autodevops/index.md
index e88b787187c..62ad1ac9956 100644
--- a/doc/topics/autodevops/index.md
+++ b/doc/topics/autodevops/index.md
@@ -496,8 +496,9 @@ The general rule is: `TRACK_ENV_REPLICAS`. Where:
That way, you can define your own `TRACK_ENV_REPLICAS` variables with which
you will be able to scale the pod's replicas easily.
-In the example below, the environment's name is `qa` which would result in
-looking for the `QA_REPLICAS` environment variable:
+In the example below, the environment's name is `qa` and it deploys the track
+`foo` which would result in looking for the `FOO_QA_REPLICAS` environment
+variable:
```yaml
QA testing:
@@ -505,11 +506,11 @@ QA testing:
environment:
name: qa
script:
- - deploy qa
+ - deploy foo
```
-If, in addition, there was also a `track: foo` defined in the application's Helm
-chart, like:
+The track `foo` being referenced would also need to be defined in the
+application's Helm chart, like:
```yaml
replicaCount: 1
@@ -531,8 +532,6 @@ service:
internalPort: 5000
```
-then the environment variable would be `FOO_QA_REPLICAS`.
-
## Currently supported languages
NOTE: **Note:**