Commerce Post Deployment Steps

After you have successfully created Self Managed Commerce environments using CloudOps for Kubernetes, you also must implement some other functionality to get a fully functional implementation. The following list of tasks is included in a typical implementation, which is not implemented as a part of CloudOps for Kubernetes. You must complete these tasks before your Self Managed Commerce environment is ready for testing and development cycles:

• Tagging and update strategy for container images to fill out the continuous integration pipeline
• Configure an SMTP or email solution
• Configure the Data Import Export tool to synchronize data from external systems
• Set up and configure the Data Sync tool to sync data from Author to Live environments

Keep Jenkins Builds

Save important Jenkins builds using the Jenkins Keep this build forever button. By doing so, you can maintain a record of the parameter values used and re-run a build to update or modify the configuration of the environment via Terraform.

You will occasionally need to update or modify the configuration of existing Self Managed Commerce environments. For example, you may need to add an IP or CIDR block to an allow-list. The proper process to update existing environments is with the Jenkins jobs used to initially configure the environment. When you re-run the job, it uses Terraform to apply any changes required. Saving builds allows you to save the parameter values used, and you can re-run those jobs and modify the parameter values as needed to make the changes that you require.

Create wrapper jobs

A recommended practice is to create your own Jenkins jobs to define the configuration of your infrastructure and environments, and to version control the source of those jobs. For example, you can define a wrapper job to deploy your production environment by writing and checking in a Jenkinsfile that calls create-or-delete-activemq-container, create-and-manage-database-server and, deploy-or-delete-commerce-stack with the specific parameter values you require to properly configure your production environment. You can check the Jenkinsfile for that job into your clone of the cloud-ops-kubernetes Git repository. Alternatively, you can use the Extensions Framework to separate these jobs in a different Git repository and include them in Jenkins. For more information see CloudOps for Kubernetes Extensions Framework.

Production Readiness Considerations

There are several common items to consider as you prepare for production-readiness. For more information, see Production Readiness Overview.