azure_storage_account_name being null still requires an external storage account

[BarryWilliams]

Issue

When deploying pcf on Azure, the params.yml says If the azure_storage_account_name is empty "", ERT will use internal storage. If you want ERT to use Azure blob store, provide a valid storage account name.

If I leave this blank, like so:
azure_storage_account_name:

Then the create-infrastructure/create-infrastructure job fails with:

Error: azurerm_storage_container.ert_storage_container_buildpacks: "name" must be between 3 and 63 characters: ""



Error: azurerm_storage_container.ert_storage_container_buildpacks: only lowercase alphanumeric characters and hyphens allowed in "name": ""



Error: azurerm_storage_container.ert_storage_container_droplets: "name" must be between 3 and 63 characters: ""



Error: azurerm_storage_container.ert_storage_container_droplets: only lowercase alphanumeric characters and hyphens allowed in "name": ""



Error: azurerm_storage_container.ert_storage_container_packages: "name" must be between 3 and 63 characters: ""



Error: azurerm_storage_container.ert_storage_container_packages: only lowercase alphanumeric characters and hyphens allowed in "name": ""



Error: azurerm_storage_container.ert_storage_container_resources: "name" must be between 3 and 63 characters: ""



Error: azurerm_storage_container.ert_storage_container_resources: only lowercase alphanumeric characters and hyphens allowed in "name": ""

Context

I have also tried
azure_storage_account_name: NULL
azure_storage_account_name: ""

I also have the following set with no value:

azure_buildpacks_container:
azure_droplets_container:
azure_packages_container:
azure_resources_container:

I don't want to have to setup an external storage account for this, I'd like to use internal.

I am using release v0.23.12

Expected result

It would use internal storage with no errors.

Current result

see above

Steps to Reproduce

see above

Possible Fix

I haven't found one yet

Logs and Screenshots

see above

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.