Using '--public-access off' when creating storage container causes creation to fail

Describe the bug

Command Name:

az storage container create

Errors:

The value for one of the HTTP headers is not in the correct format. ErrorCode: InvalidHeaderValue
<?xml version="1.0" encoding="utf-8"?><Error><Code>InvalidHeaderValue</Code><Message>The value for one of the HTTP headers is not in the correct format.
RequestId:9821f33d-c01e-00e5-78a7-171d7d000000
Time:2020-04-21T06:39:11.6688523Z</Message><HeaderName>x-ms-blob-public-access</HeaderName><HeaderValue>off</HeaderValue></Error>

To Reproduce:

• az storage container create --name {} --account-name {} --account-key {} --public-access off

Expected Behavior

A more meaningful error message stating that setting public-access is no longer needed in the latest version.

Environment Summary

Linux-5.5.17-200.fc31.x86_64-x86_64-with-fedora-31-Thirty_One
Python 3.7.6
Installer: RPM

azure-cli 2.4.0

Also tested in:

Linux-5.0.0-1036-azure-x86_64-with-debian-buster-sid
Python 3.6.5
Installer: DEB

azure-cli 2.4.0

Additional Context

Removing the public-access parameter entirely or setting a value of either blob or container will not cause issues.

[usrme]

Oh, damn! I must’ve missed that as I was sure that the default permission was to deny public access.

EDIT:

@flytzen, I just tested creating a storage container with the following command: az storage container create --name "$1" --account-name "$2" --account-key "$3", which resulted in a storage container that has the Public access level as Private when viewing the container in the Azure Portal. Am I missing something crucial?

$ az version
{
  "azure-cli": "2.4.0",
  "azure-cli-command-modules-nspkg": "2.0.3",
  "azure-cli-core": "2.4.0",
  "azure-cli-nspkg": "3.0.4",
  "azure-cli-telemetry": "1.0.4",
  "extensions": {}
}

[Juliehzl]

dupe of #13373 Fixed in azure cli 2.6.0