Unable to use artifacts function to specify roleDefinitionId. about azure-blueprints HOT 3 OPEN

Basically we check that you have access to the role definition when you create the blueprint definition. We are not able to do that if it's parameterized. If you are not using the blueprint lock capability, then I'd recommend using bicep + template specs as this will give you full control to parameterize any field. You may want to check out this video:
https://www.youtube.com/watch?v=i4dEN0o1PHo

from azure-blueprints.

So there's an up-front check on the role definition when you create the blueprint definition, if I understood you correctly.
Have you considered doing this check during assignment/deployment instead?

Also yes, I do use the lock capability and intend to keep doing so. ☹️

I will have a look at the video later. 😄

from azure-blueprints.

I have now had a look at the video you linked. It looks like the Bicep approach has the same issue as ARM, as it is essentially just ARM with a nicer syntax and functionality. Having to come up with your own GUID for the role assignment is something we would like to avoid.

from azure-blueprints.