Feature Request: Allow secret names to be greater than 20 characters

[sunniejai]

In previous versions of the container apps, you could have secret names that are longer than 20 characters. Example: applicationinsightsinstrumentationkey, but starting this week, I started getting an error saying that ERROR: Secret names cannot be longer than 20. Please shorten applicationinsightsinstrumentationkey.

I'm not sure why we're forcing people to use shorter names? 20 characters isn't very long at all.

Please allow secret names > 20 characters again.

[torosent]

Thanks @sunniejai. We have a work item o change it.

[sunniejai]

Any updates on when this will be worked on? Still seeing this issue

[sunefred]

Looking forward to this as well! We are having to make a lot of nonsensical abbreviations to fit the length requirement. In the meantime there does not seem to be any restrictions in the UI at all.

[mgelei]

On a sidenote, you can't even update existing secrets that were created automatically upon creating the app, see #728

[shaikmoeed]

Hi, @torosent Is there any update on this? We are having many container apps where we need to update the secret value of all those container apps. Doing it through UI is a very long task, any workaround or fixing for this bug would help a lot.

[howang-ms]

The length limit for secret name is extended to 63 char now.

[shaikmoeed]

@howang-ms Still getting same error. Is there anything need to update on CLI or this change is not yet deployed?

[adrobson]

Why is there such a short limit? To set up KEDA scaling on a Azure Storage Queue there needs to be a reference to the Storage Account Connection String (not the Account Key), which needs to be stored as a secret. In my case the connection string is 188 characters which would be fairly typical. So therefore shouldn't the limit be 300 characters or so? Otherwise how else could we set up an environment completely using Devops automation?

[mgelei]

@adrobson The limitation is for the name of the secret, thus storing a connection string should be fine, as long as the name for the actual key vault entry is less than 63 characters long.

[mshasib]

Has this been fixed? Secret key names greater than 20 characters can be added from the portal but still see the issue on the CLI

[pupul07]

Can confirm that the CLI still doesn't allow more than 20 characters :(
Hope this gets fixed soon!