Open isaacabraham opened 2 years ago
Sounds like it’s the same as this https://github.com/microsoft/azure-container-apps/issues/153
Ok, at least I'm not imagining things! Thanks
Just hit this as well, this line does not pass the template validation, which I think is a different issue - ARM doesn't seem to be evaluating the name expression, treating it as a constant instead.
@et1975 that's exactly the same issue :-)
I was referring to the linked ARM/biceps issue, which is specifically about naming of the registry. The PR I have opened fixed both issues.
I see! I think it's the same underlying issue - ARM isn't evaluating expressions in the template in certain fields.
The fix you've put in is of course a really nice workaround, by not using an ARM expression at all.
@isaacabraham - looking to close this one if the fix solved the issue?
Something is up with the Container App / Container Registry integration. I could swear that this worked a month or so ago, but I tried creating a new container app service today. This is the offending line:
where
mySuperRegistry
is an Azure container registry that already exists.When I try an deploy the container app, I get the following validation error:
Here's an extract of the raw ARM template:
It's almost as though ARM hasn't seen that secrets.name is an expression, and has instead tried to parse the expression as a raw string.
@ninjarobot Have you any idea about this - or if this ever used to work? @anthonychu has anything changed in the way that secret names are handled in terms of ARM template support - maybe something has changed since the namespace move?