-
Notifications
You must be signed in to change notification settings - Fork 97
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.
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
Add disclaimer about customer-owned and spryker-owned variables #1942
Conversation
|
||
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. However, please note that changes to these variables do not automatically propagate into the running environment. To apply changes made to your environment variables, you'll need to run an ECS-updater-* pipeline in order to bring them to the containers (full re-deploy would also do the trick, of course). This process does not require Spryker Cloud or support intervention. | ||
|
||
On the other hand, Spryker-owned environment variables should not be altered directly in the Parameter Store. These variables have been configured by Spryker for the optimal operation of the Cloud Commerce OS. Any change made directly to these variables can introduce inconsistencies and potential issues in Cloud Operations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in optimal situations (proper IAM roles, and well-migrated old vars in case of existing customers), customers won't see those variables if they access the Param Store. they will have only the right to CRUD their own vars under the dedicated paths.
Worst case scenario, if these variables are still visible, the IAM roles won't let them edit them.
|
||
On the other hand, Spryker-owned environment variables should not be altered directly in the Parameter Store. These variables have been configured by Spryker for the optimal operation of the Cloud Commerce OS. Any change made directly to these variables can introduce inconsistencies and potential issues in Cloud Operations. | ||
|
||
If there is a need to modify a Spryker-owned environment variable, it must be done through Terraform to ensure proper application and consistency. However, such changes require Spryker Cloud or support intervention, as it needs to be coordinated with our DevOps team. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove the terraform part.
i suggest :
If there is a need to modify a Spryker-owned environment variable, it must be done through Spryker Cloud or Support intervention, as it needs to be coordinated with our DevOps team to ensure proper application and consistency.
Updated, considering comments from Hatem
|
||
When working with environment variables in the Spryker Cloud Commerce OS, it's important to understand that there are two types of variables: those owned by the customer and those owned by Spryker. | ||
|
||
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. However, please note that changes to these variables do not automatically propagate into the running environment. To apply changes made to your environment variables, you'll need to run an ECS-updater-* pipeline in order to bring them to the containers (full re-deploy would also do the trick, of course). This process does not require Spryker Cloud or support intervention. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@feversocial "This process does not require Spryker Cloud or support intervention." - what does it mean "does not require Spryker Cloud intervention"?
PR Description
TBD
Checklist