Closed thekaveman closed 3 months ago
This PR does not seem to contain any modification to coverable code.
Front-end tests are failing because they build a container with these changes against docker-python-web:main
, without the changes from cal-itp/docker-python-web/pull/42
terraform plan
indicates the expected changes to the storage_account
reflecting that the mount location changed from /home/calitp/app/data
to /calitp/app/data
.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# azurerm_linux_web_app.main will be updated in-place
~ resource "azurerm_linux_web_app" "main" {
id = "/subscriptions/xxx/resourceGroups/RG-CDT-PUB-VIP-CALITP-D-001/providers/Microsoft.Web/sites/AS-CDT-PUB-VIP-CALITP-D-001"
name = "AS-CDT-PUB-VIP-CALITP-D-001"
tags = { ... }
# (21 unchanged attributes hidden)
- storage_account {
# At least one attribute in this block is (or was) sensitive,
# so its contents will not be displayed.
}
+ storage_account {
# At least one attribute in this block is (or was) sensitive,
# so its contents will not be displayed.
}
# (4 unchanged blocks hidden)
}
Plan: 0 to add, 1 to change, 0 to destroy.
Part of #2153
Related to:
This PR should be merged after the one in
docker-python-web
.From that PR's description:
Testing locally
Build the
benefits_client
, ensuring thedocker-python-web
digest SHA matches the expected digest SHA:sha256:c937ae01afebab96473045c3a0f3aa9c3a28609d1ff33d756740d2eea254c61f
And restart the devcontainer in VS Code. Then run the app as normal with F5.