-
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
New Data Source: azurerm_automation_account
#4740
New Data Source: azurerm_automation_account
#4740
Conversation
…it was very long, Azure Portal describes it as Keys in the User Interface
…ding newline (whitespace) for linttravis to pass
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @whytoe, this mostly looks good but azurerm.erb
had some extra removals and white space additions that should be addressed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
azurerm_automation_account
Good call @whytoe. It looks like this does close that issue as well. Thanks! |
This has been released in version 1.37.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 1.37.0"
}
# ... other configuration ... |
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! |
This Data provider exposes the Keys property in Azure Portal for Automation Account, it uses the goSDK function ".Automation.AgentRegistrationInfoClient" in the ARM client.
I wouldnt be opposed to renaming the data source to be more descriptive but I thought it might be a good idea to expand on this data source for all the automation account properties instead of maintaining multiple data providers for the same resource.