GitLab CI

As you may have heard before, in order for ShamanOps to work properly, you must add some variables and secrets to your CI platform. You can find how to do it in GitLab in this documentation: Add variables and secrets in GitLab

Manually

This is what you should add:

1. Add Variables

---

shamanops_customer_id *
This value will be sent by the ShamanOps team after registration.
Example: 2

shamanops_argocd_dev_url *
You will get this data after the ShamanOps was successfully installed.
Example: argocd.apps.customer.com

shamanops_argocd_dev_user *
You will get this data after the ShamanOps was successfully installed.
Example: user

shamanops_argocd_stg_url *
You will get this data after the ShamanOps was successfully installed.
Example: argocd.apps.customer.com

shamanops_argocd_stg_user *
You will get this data after the ShamanOps was successfully installed.
Example: user

shamanops_argocd_prod_url *
You will get this data after the ShamanOps was successfully installed.
Example: argocd.apps.customer.com

shamanops_argocd_prod_user *
You will get this data after the ShamanOps was successfully installed.
Example: user

shamanops_argocd_drp_url *
You will get this data after the ShamanOps was successfully installed.
Example: argocd.apps.customer.com

shamanops_argocd_drp_user *
You will get this data after the ShamanOps was successfully installed.
Example: user

shamanops_code_quality_url *
This value is provided by the customer and refers to SonarQube endpoint URL.
Example: https://sonarqube.customer.com

shamanops_manifest_repository *
This value is provided by the customer and refers to the HTTPS URL of manifest repository in GIT platform.
Example: https://github.com/customer/manifests.git

shamanops_manifest_repository_user *
This value is provided by the customer and refers to the username to access the manifest repository in GIT platform.
Example: user

shamanops_registry_url *
This value is provided by the customer and refers to the container registry specific URL.
Example: ghcr.io/customer

shamanops_registry_user *
This value is provided by the customer and refers to the username to access the container registry.
Example: user

shamanops_chat_webhook *
This value is provided by the customer and refers to the webhook of the chat platforms channel.
Ex: https://chat.googleapis.com/v1/spaces/xxxx/messages?key=xxx&token=xxxx

2. Add Secrets 🔒

---

shamanops_customer_token *
🔒 This value will be sent by the ShamanOps team after registration.

shamanops_argocd_dev_token *
🔒 You will get this data after the ShamanOps was successfully installed.

shamanops_argocd_stg_token *
🔒 You will get this data after the ShamanOps was successfully installed.

shamanops_argocd_prod_token *
🔒 You will get this data after the ShamanOps was successfully installed.

shamanops_argocd_drp_token *
🔒 You will get this data after the ShamanOps was successfully installed.

shamanops_code_quality_token *
🔒 This value is provided by the customer and refers to SonarQube Access Token.

shamanops_manifest_repository_token *
🔒 This value is provided by the customer and refers to the PAT to access the manifest repository in GIT platform.

shamanops_registry_password *
🔒 This value is provided by the customer and refers to the token to access the container registry.

shamanops_dockerfile_token *
🔒 This value refers to a token that can be used at build time, it was thought to connect artifact repositories like Nugets. This must be defined even if it is not used, containing some sort of value.

DOCKER_AUTH_CONFIG *
🔒 This value will be sent by the ShamanOps team after registration.

With assistance

1. Execute the following command

shamanops_bs_gitlab_assistance yourMainGroupName

info

Please remember to replace yourMainGroupName for the respective name of your Main Group

You should get this output:

2. Execute the commands