dto-btn/infrastructure

General infrastructure of DTO team.

infrastructure

General infrastructure of DTO team.

This is split by environments, and we currently only have environments in Azure, so we use their zoning to group project/modules together.

The 3 main environments at SSC inside Azure:

• Sandbox (ScSc),
• Dev (ScDc),
• Prod (ScPc)

So we end up with this structure:

• live
  • dev
    • chatbot
    • projectB
  • sandbox
    • chatbot
    • projectC

And so on ..

dev

First make sure you have all the pre-requisites.

In order to run a specific subset (for instance, I want to setup chatbot in sandbox):

cd live/sandbox/chatbot
terragrunt plan --terragrunt-source ~/git/chatbot-infra/chatbot

Ignore --terragrunt-source if you would rather use the true source value from the terraform block in the terragrunt.hcl (in most case, remote github source)

pre-requisites

You will need those tools:

• terraform
• terragrunt
• az client

And make sure you have created a secret.tfvars at the root folder and populate it with the following.. But all variables below can also be defined in the environments with prefix TF_VAR_ instead (ex: TF_VAR_dev_sub_id).

personal_token="<github-secret-to-pull>"
microsoft_provider_authentication_secret="<provided-by-infra-team-secret>"

You also need to create at the root of the repo a local-secrets.hcl file and populate the following content:

(subscription ids are considered non sensitive but in this case we are taking an extra precaution)

locals {
    dev = {
        subscription_id = "<sub_id>"
        tenant_id = "<secret>"
        client_id = "<secret>"
        client_secret = "<secret>"
    }

    sandbox = {
        ...
    }
}

NOTE: Messing things up above could yeild pretty bad consequences...

infrastructure's Issues

chatbot dev (pilot) deployment

• run terragrunt apply on the live/dev/chatbot section to bring up to date the dev (pilot) env.
• ensure all services are running and up to date meeting the sandbox