Open geohacker opened 1 year ago
Great idea!
Thanks @geohacker .
Yea, this was likely an error in judgement on my part: it seemed great and convenient to have it all in a single code-base. But as we've worked on it, it is increasingly seeming much more practical / easy to deal with if we split this up into a separate repository.
This is mostly for developer experience and convenience, it's not a blocker to the current work. So we should probably finish testing the whole setup with the current approach and then we can weigh the benefits and also work involved to split this out into a separate repository.
This is close to ready!
@sunu could you outline a checklist for next steps here and things we need to ensure as we do this move? Thanks!
Outlining the next steps below to move infrastructure code out of this repository to go-deploy repository:
terraform plan
against the staging cluster through the newly setup Azure pipeline--dry-run
flag--dry-run
flag, change terraform plan
to terraform apply
and do a staging deployment
The continuous deployment work that is underway in #1725 is currently tied to this repository along with the codebase. It will be good to make this a separate repo so that:
This means that we will:
deploy
folder https://github.com/IFRCGo/go-api/tree/terraform/deploy to a new repocc @batpad @szabozoltan69