finalize

spryker · Feb 6, 2025 · 5fad226 · 5fad226
1 parent d45a30d
commit 5fad226
Show file tree

Hide file tree

Showing 2 changed files with 31 additions and 26 deletions.
diff --git a/Rakefile b/Rakefile
@@ -97,9 +97,11 @@ commonOptions = {
     /www.jetbrains.com\/[\.\w\-\/\?]+/,
     /docs.spring.io\/[\.\w\-\/\?]+/,
     /redisdesktop.com\/[\.\w\-\/\?]+/,
+    /jwt.io\/[\.\w\-\/\?]+/,
     /developer.computop.com\/[\.\w\-\/\?]+/,
     /www.centralbank.cy\/[\.\w\-\/\?]+/,
-    /www.gnu.org\/[\.\w\-\/\?]+/,    
+    /www.mysql.com\/[\.\w\-\/\?]+/,
+    /www.gnu.org\/[\.\w\-\/\?]+/,
     /algolia.com\/[\.\w\-\/\?]+/,
     /www.facebook.com\/[\.\w\-\/\?]+/
 

diff --git a/docs/ca/dev/add-variables-in-the-parameter-store.md b/docs/ca/dev/add-variables-in-the-parameter-store.md
@@ -29,9 +29,34 @@ For complex or system-critical changes to variables, we recommend consulting wit
 
 There are two types of environment variables: customer-owned and Spryker-owned.
 
-Customer-owned variables are created and managed by you—the onboarded customer or implementation partner. You have full control over these variables and can add or edit them according to your needs. Changes to these variables don't automatically propagate into a running environment. To apply changes made to your environment variables, you need to run an ECS-updater-* pipeline to bring them to the containers or run a full redeploy. You can do this whole process without creating support tickets.
+Spryker-owned variables are managed and can be updated only with the help of Spryker Cloud or support teams.
+
+Customer-owned variables are created and managed by you or implementation partner. You have full control over these variables and can add or edit them according to your needs. Changes to these variables don't automatically propagate into a running environment. To apply changes made to your environment variables, you need to run an ECS-updater-* pipeline to bring them to the containers or run a full redeploy. You can do this whole process without creating support tickets.
+
+### Customer-owned variables with limited access
+
+The following customer-owned variables can be updated only with the help of Spryker Cloud or support teams:
+
+* /{project}/{environment}/secret/scheduler/limited/{variable_name}
+
+* /{project}/{environment}/secret/pipeline/limited/{variable_name}
+
+* /{project}/{environment}/secret/infra/limited/{variable_name}
+
+* /{project}/{environment}/secret/common/limited/{variable_name}
+
+* /{project}/{environment}/secret/app/limited/{variable_name}
+
+* /{project}/{environment}/config/scheduler/limited/{variable_name}
+
+* /{project}/{environment}/config/pipeline/limited/{variable_name}
+
+* /{project}/{environment}/config/infra/limited/{variable_name}
+
+* /{project}/{environment}/config/common/limited/{variable_name}
+
+* /{project}/{environment}/config/app/limited/{variable_name}
 
-You can update Spryker-owned variables with the help of Spryker Cloud or support team.
 
 ## Naming convention for variables
 
@@ -101,7 +126,7 @@ Reserved variables:
 * `TIDEWAYS_CLI_ENABLED`
 * `TIDEWAYS_DAEMON_URI`
 * `TIDEWAYS_ENVIRONMENT`
- 
+
 
 
 ## Variable path hierarchy
@@ -134,28 +159,6 @@ The following variables are arranged from lower to higher priority:
 
 The following sections describe how to add parameters and secrets for different resources.
 
-**Note:** The next variables should be requested by a ticket on [Support Portal](https://support.spryker.com/) in "(Infrastructure Change Request > Change to existing parameter store variable)"
-
-* /{project}/{environment}/secret/scheduler/limited/{variable_name}
-
-* /{project}/{environment}/secret/pipeline/limited/{variable_name}
-
-* /{project}/{environment}/secret/infra/limited/{variable_name}
-
-* /{project}/{environment}/secret/common/limited/{variable_name}
-
-* /{project}/{environment}/secret/app/limited/{variable_name}
-
-* /{project}/{environment}/config/scheduler/limited/{variable_name}
-
-* /{project}/{environment}/config/pipeline/limited/{variable_name}
-
-* /{project}/{environment}/config/infra/limited/{variable_name}
-
-* /{project}/{environment}/config/common/limited/{variable_name}
-
-* /{project}/{environment}/config/app/limited/{variable_name}
-
 ### Add parameters to all resource types
 
 1. In the AWS Management Console, go to **Services&nbsp;<span aria-label="and then">></span> Parameter Store**.