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
Description
Currently, the only way to deploy and manage PowerShell modules in Azure Automation is to supply a URI. The portal lets you choose a module from the modules gallery. Thhis make managing modules complicated as you have to download the module and upload it to your own storage account and repeat the process every time a new version comes out.
The text was updated successfully, but these errors were encountered:
humanascode
changed the title
Support for deploying PowerShell modules from the gallery (and not using a uri)
Support for deploying PowerShell modules from the gallery (and not using a uri) in azurerm_automation_module
Mar 13, 2023
Hi @itamar56 thanks for you feedback, i believe this feature request is very much reasonable. but for now, the gallery modules cannot managed by terraform and there isn't such API fot azurerm to featch the gallery module list.
Is there an existing issue for this?
Community Note
Description
Currently, the only way to deploy and manage PowerShell modules in Azure Automation is to supply a URI. The portal lets you choose a module from the modules gallery. Thhis make managing modules complicated as you have to download the module and upload it to your own storage account and repeat the process every time a new version comes out.
New or Affected Resource(s)/Data Source(s)
azurerm_automation_module
Potential Terraform Configuration
References
No response
The text was updated successfully, but these errors were encountered: