-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement data source for azurerm_automation_dsc_configuration_metadata #2162
Comments
The resource already supports outputting the Primary Key/DSC Server Endpoint Is there a blocker for this? @tombuildsstuff |
@bastienfrancheteau were you able to find another solution other than use powershell? @tombuildsstuff does the GoSDK support this now, its been almost a year It is available in powershell
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Community Note
When registering a VM as a DSC node, the Automation Account's key and DSC Registration URL values are required. These cannot be retrieved in Terraform. Creating an azurerm_automation_dsc_configuration_metadata module that returns these 2 values would enable us to dynamically register Azure VMs as DSC nodes.
Suggested name for new data source: azurerm_automation_dsc_configuration_metadata
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: