optionals configurations for Cosmo Tech tenants
- working Kubernetes tenant deployed from Cosmo Tech terraform-tenant
- terraform
- clone & open the repository
git clone https://github.com/Cosmo-Tech/terraform-extra.git --branch <tag> cd terraform-extra - deploy
- fill
terraform.tfvarsvariables according to your needs - run pre-configured script
- plan
get an execution plan to preview the changes without applying
- Linux
./_run-terraform.sh - Windows
./_run-terraform.ps1
- Linux
- apply
executes the operations proposed in the plan
- Linux
./_run-terraform.sh --apply - Windows
./_run-terraform.ps1 --apply
- Linux
- plan
- fill
- None known error for now !
resolution description will takes place here
- modules
- terraform-extra
- config_keycloak_idp = add an Identity Provider on the top of an existing Keycloak (for exemple set Okta as IdP for Keycloak)
- terraform-extra
- Terraform state
- The state is stored beside the cluster Terraform state, in the current cloud s3/blob storage service (generally called
cosmotech-statesorcsmstates<id>, depending on what the cloud provider allows in naming convention)
- The state is stored beside the cluster Terraform state, in the current cloud s3/blob storage service (generally called
Made with ❤️ by Cosmo Tech DevOps team