Skip to content

Fix #548: use storage_container_id for azurerm_storage_blob#552

Merged
doherty100 merged 2 commits into
vnextfrom
fix/548-storage-blob-container-id
Jul 8, 2026
Merged

Fix #548: use storage_container_id for azurerm_storage_blob#552
doherty100 merged 2 commits into
vnextfrom
fix/548-storage-blob-container-id

Conversation

@doherty100

Copy link
Copy Markdown
Contributor

Closes #548

Problem

storage_account_name and storage_container_name on azurerm_storage_blob are deprecated in favor of storage_container_id and will be removed in v5.0 of the azurerm provider (see the resource docs).

Changes

  • vnet-app: azurerm_storage_blob.remote_scripts now uses storage_container_id = azurerm_storage_container.this.id. The container ID is also exposed via resource_ids["storage_container"].
  • vm-mssql-win: azurerm_storage_blob.remote_scripts now uses a new storage_container_id input (replacing the now-unused storage_account_name input). Wired from the root module via module.vnet_app[0].resource_ids["storage_container"].
  • Updated the vm-mssql-win README inputs table.

storage_container_name is retained in vm-mssql-win because it is still used to build the run-command fileUris.

Validation

  • terraform validate — passes (only a pre-existing, unrelated local_authentication_disabled deprecation warning).
  • terraform fmt -check — clean.
  • tflint — clean.

doherty100 and others added 2 commits July 8, 2026 13:34
storage_account_name and storage_container_name on azurerm_storage_blob
are deprecated in favor of storage_container_id and will be removed in
azurerm provider v5.0. Update the remote_scripts blobs in the vnet-app
and vm-mssql-win modules to use storage_container_id.

- vnet-app: reference azurerm_storage_container.this.id directly and
  expose it via resource_ids["storage_container"].
- vm-mssql-win: add a storage_container_id input (replacing the now
  unused storage_account_name input) and wire it from the root module.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@doherty100 doherty100 merged commit ca7e52c into vnext Jul 8, 2026
16 checks passed
@doherty100 doherty100 deleted the fix/548-storage-blob-container-id branch July 8, 2026 17:40
@doherty100

Copy link
Copy Markdown
Contributor Author

✅ Testing results

Deployed a fresh sandbox on vnext (with this change merged, commit ca7e52c) to validate PR #552, enabling only the affected modules.

Environment

  • Modules: vnet_shared (required) + vnet_app + vm_mssql_win
  • Location: centralus
  • Terraform v1.15.7 · azurerm v4.80.0 · azapi v2.10.0

PR change validated during apply — both storage_container_id conversions uploaded their blobs successfully:

  • vnet_appazurerm_storage_blob.remote_scripts (orchestrator, worker)
  • vm_mssql_winazurerm_storage_blob.remote_scripts (orchestrator, startup, worker)

Unit + integration tests — RESULT: PASS (53/53, 0 failed)

Scope Result
vnet-shared Passed=9 Failed=0
vnet-app Passed=18 Failed=0
vm-mssql-win Passed=25 Failed=0
integration — SQL: jumpwin1 → mssqlwin1 Passed=1 Failed=0
Overall Passed=53 Failed=0

The storage_container_id change works correctly for both modules, and all deployed-module tests pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant