Open Zhiyuan-Amos opened 2 years ago
[Enhancement] Rollback is required to support the scenario:
Such that when any of these steps fail, it should rollback to the previous version.
[Enhancement] How do we spin up a new environment & run tests after new commits are merged into master?
[Enhancement] Do we spin up a new env on PR created?
Likely have 3 environments: Dev, Test, Prod. Test environment will be dynamically created after new commits are merged into master.
Does monolithic deployment consisting of several steps a good practice? As each service is being updated individually, this can lead to bugs occurring if the caller service is updated but the callee service hasn't been updated. Should it be rectified on the code level where the code provides backward compatibility?
Currently, we're performing Azure Login with OpenID Connect(OIDC) and use it in a GitHub Actions. However, Terraform have yet to support OIDC in their Terraform configurations here: https://github{dot}com/hashicorp/terraform-provider-azurerm/issues/16554
Also consider: