summaryrefslogtreecommitdiff
path: root/doc/downgrade_ee_to_ce
diff options
context:
space:
mode:
authorLin Jen-Shin <godfat@godfat.org>2017-07-06 15:45:38 +0800
committerLin Jen-Shin <godfat@godfat.org>2017-07-06 16:25:03 +0800
commitd9435d61218f677395f3b53976a41ac5f361f24b (patch)
treedaeffa17eef21005694cea90eb300b359d433b66 /doc/downgrade_ee_to_ce
parent2520edefb9a7481f575ac7bcdbcf89cb1432f27d (diff)
downloadgitlab-ce-d9435d61218f677395f3b53976a41ac5f361f24b.tar.gz
Backports for ee-2112
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2112
Diffstat (limited to 'doc/downgrade_ee_to_ce')
-rw-r--r--doc/downgrade_ee_to_ce/README.md13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/downgrade_ee_to_ce/README.md b/doc/downgrade_ee_to_ce/README.md
index fe4b6d73771..75bae324585 100644
--- a/doc/downgrade_ee_to_ce/README.md
+++ b/doc/downgrade_ee_to_ce/README.md
@@ -46,6 +46,19 @@ $ sudo gitlab-rails runner "Service.where(type: ['JenkinsService', 'JenkinsDepre
$ bundle exec rails runner "Service.where(type: ['JenkinsService', 'JenkinsDeprecatedService']).delete_all" production
```
+### Secret variables environment scopes
+
+If you're using this feature and there are variables sharing the same
+key, but they have different scopes in a project, then you might want to
+revisit the environment scope setting for those variables.
+
+In CE, environment scopes are completely ignored, therefore you could
+accidentally get a variable which you're not expecting for a particular
+environment. Make sure that you have the right variables in this case.
+
+Data is completely preserved, so you could always upgrade back to EE and
+restore the behavior if you leave it alone.
+
## Downgrade to CE
After performing the above mentioned steps, you are now ready to downgrade your