-
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 Resource: azurerm_monitor_data_collection_rule_association
#17948
New Resource: azurerm_monitor_data_collection_rule_association
#17948
Conversation
…m into monitor_data_collection_rule_association
…m into monitor_data_collection_rule_association
website/docs/r/monitor_data_collection_rule_association.html.markdown
Outdated
Show resolved
Hide resolved
|
||
The following arguments are supported: | ||
|
||
* `name` - (Required) The name which should be used for this Data Collection Rule. Changing this forces a new Data Collection Rule to be created. |
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.
if this cannot be configured to anything but configurationAccessEndpoint should we even be exposing the name? maybe we should remove it>
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.
Like mentioned above, if data_collection_rule_id
is configured, then the name can be customized. I am going to add this in the doc.
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.
they it sounds like this property should be optional and only required when data_collection_rule_id is configured, and if it is we populate it with configurationAccessEndpoint ?
…m into monitor_data_collection_rule_association
…m into monitor_data_collection_rule_association
…m into monitor_data_collection_rule_association
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 🦺
This functionality has been released in v3.22.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
} | ||
|
||
# associate to a Data Collection Endpoint | ||
resource "azurerm_data_collection_rule_association" "example1" { |
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.
should this be named example2? I tried pasting the code from https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/monitor_data_collection_rule_association and hit a 'example1' already exists error from the resource above defined on line 96
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.
also line 106, data_collection_endpoint_id = azurerm_monitor_data_collection_endpoint.test.id
?
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.
Thanks for pointing this out, I have submitted another PR #18536 to fix this.
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
New resource
azurerm_monitor_data_collection_rule_association
Resolves #17831
Reference:
Test Result