Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploy to test #355

Merged
merged 71 commits into from
Oct 26, 2023
Merged

Deploy to test #355

merged 71 commits into from
Oct 26, 2023

Conversation

angela-tran
Copy link
Member

No description provided.

angela-tran and others added 30 commits September 26, 2023 19:23
github.ref_name covers getting either branch _or tag_ name, so with this
commit, a run of this workflow would publish a Docker tag with the git
tag name
also set 'cancel-in-progress' to true so that pending runs will cancel
if a newer run is queued for a given concurrency group
the workflow itself is already filtered to only listen to
release publishes
maintain access to healthcheck endpoint
put the expression back as inline values instead of being a variable
backend configuration cannot use named values such as variables
angela-tran and others added 20 commits October 10, 2023 22:52
remove Build Status badge; it seems to not render correctly
update README to point to online documentation
updates:
- [github.com/psf/black: 23.9.1 → 23.10.0](psf/black@23.9.1...23.10.0)
this will rename MST's key vault
@angela-tran angela-tran added this to the SBMTD Mobility Pass milestone Oct 26, 2023
@angela-tran angela-tran self-assigned this Oct 26, 2023
@angela-tran angela-tran requested a review from a team as a code owner October 26, 2023 19:11
@thekaveman
Copy link
Member

thekaveman commented Oct 26, 2023

Can we make #253 go as part of this cycle?

Nevermind we're not going to try and do this at the same time.

@thekaveman
Copy link
Member

@angela-tran the plan failed, is that expected?

Error: Instance cannot be destroyed

│ on key_vault.tf line 1:
│ 1: resource "azurerm_key_vault" "main" {

│ Resource azurerm_key_vault.main has lifecycle.prevent_destroy set, but the
│ plan calls for this resource to be destroyed.

Seems like the same message as before?

@thekaveman
Copy link
Member

Is this where we need to soft-delete the key vault and not worry since we're not trying to reuse the name anyway?

@angela-tran
Copy link
Member Author

@angela-tran the plan failed, is that expected?

Error: Instance cannot be destroyed

│ on key_vault.tf line 1:
│ 1: resource "azurerm_key_vault" "main" {

│ Resource azurerm_key_vault.main has lifecycle.prevent_destroy set, but the
│ plan calls for this resource to be destroyed.

Seems like the same message as before?

Right, it's the same message as when we plan'd the change in #354 for dev. So now we need to do the same process of manually deleting the Key Vault (this time the one named eligibility-server-test) and setting the secret again in the new mst-courtesy-card-test Key Vault

@angela-tran angela-tran merged commit b213928 into test Oct 26, 2023
13 checks passed
@angela-tran angela-tran mentioned this pull request Oct 31, 2023
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants