[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)
Issue description
When you create a container app with an external registry (e.g. GHCR) it creates a secret to store the token needed to log in. But when I try to update the token through Azure CLI, I get an error message: "Secret names cannot be longer than 20."
Steps to reproduce
Create container app on Azure portal, with an image from GHCR
Create a GH personal token and give it to the app so it can access private packages
Regenerate the token (i.e. upon expiry) and run: az containerapp secret set -n MyApp -g MyRG --secrets reg-pswd-abcd1234-ab12=MySecretToken, where reg-pswd-abcd1234-ab12 is the name of the secret automatically generated upon the app's creation
Expected behavior [What you expected to happen.]
The secret value gets replaced by the new value
Actual behavior [What actually happened.]
ERROR: Secret names cannot be longer than 20. Please shorten reg-pswd-abcd1234-ab12 and exits with code 1
This issue is a: (mark with an x)
Issue description
When you create a container app with an external registry (e.g. GHCR) it creates a secret to store the token needed to log in. But when I try to update the token through Azure CLI, I get an error message: "Secret names cannot be longer than 20."
Steps to reproduce
az containerapp secret set -n MyApp -g MyRG --secrets reg-pswd-abcd1234-ab12=MySecretToken
, where reg-pswd-abcd1234-ab12 is the name of the secret automatically generated upon the app's creationExpected behavior [What you expected to happen.] The secret value gets replaced by the new value
Actual behavior [What actually happened.] ERROR: Secret names cannot be longer than 20. Please shorten reg-pswd-abcd1234-ab12 and exits with code 1