docs: added basic deployment.

[pantierra]

Started documenting the deployment flow. Not sure if this is as it should be/actually is. But let's use this PR to consolidate it.

[pantierra]

One thing I am realizing that is causing confusion:

• We have two branches develop and master, whereas it seems master is currently not used, but the setup gives the impression that staging and production differentiate depending to which branch it is deployed.
• We have two folders under applications/argocd which are staging and production that give the impression that staging and production differentiate depending on which folder it is specified.

I suggest to get rid of either one of those, so either use different folders/files but one clear branch, e.g. main (instead of develop and master), or one folder argocd and deploy it depending on production and staging branches.

[thenav56]

Thanks @pantierra for this.

Right now we have a kind of documentation in the apps-of-app manifest (it has the branch, exclude patterns, and so on)

• https://github.com/IFRCGo/go-deploy/blob/develop/applications/argocd/production.yaml
• https://github.com/IFRCGo/go-deploy/blob/develop/applications/argocd/staging.yaml

There are also docs in the argocd directory: https://github.com/IFRCGo/go-deploy/blob/develop/applications/argocd/README.md. Do you think we should put your changes there instead?

If you like, put the aggregated docs in docs/deployment.md.

---

Right now, terraform and argocd have different deployment flows.

• Terraform
  • Same directory for staging and production
  • Settings are defined with an if-check on the environment name
  • develop is for staging and master is for production
  • Uses the azure pipeline for deployment (Each branch includes separate credentials for Azure)
    • go-api is also handle by this, we are in-progress of moving this to argocd
• Argocd
  • Separate directory for staging and production
  • Settings are defined on their own, in raw form
  • develop is for both staging and production

---

In future, I am planning to discuss and implement to split this repo into 2 new repos:

• go-deploy-tf — use staging and production as branches
• go-deploy-argocd — use main as the branch