You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Versions
Please paste the output of terraform version command from within the initialized directory:
terraform 1.9.5
azurerm 3.99.0
azapi 1.14.0
time 0.11.2
Please enter the module version that you are using:
Used 2 versions of the module, same behaviour:
Versions: 4.1.2 & 4.1.3
Description
Creating UMI with following configuration calling the module:
Both resource groups will be created by the module as well and locks disabled after problems assigning permissions to them.
This is my output each time my pipeline is running (expected "no changes"). I get the same when I run it on my container with terraform version 1.9.1 & azapi 1.14.0 & azurerm 3.99.0 & time 0.11.2
Steps to Reproduce
Create UMI with the above configuration and it should be the same behaviour.
The text was updated successfully, but these errors were encountered:
Community Note
Versions
Please paste the output of
terraform version
command from within the initialized directory:Please enter the module version that you are using:
Description
Creating UMI with following configuration calling the module:
Both resource groups will be created by the module as well and locks disabled after problems assigning permissions to them.
This is my output each time my pipeline is running (expected "no changes"). I get the same when I run it on my container with terraform version 1.9.1 & azapi 1.14.0 & azurerm 3.99.0 & time 0.11.2
Steps to Reproduce
Create UMI with the above configuration and it should be the same behaviour.
The text was updated successfully, but these errors were encountered: