Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support: Refer sentinel automation rule resource as a automated response in azurerm_sentinel_alert_rule_scheduled #26544

Open
1 task done
mounikakandagadda29 opened this issue Jul 5, 2024 · 2 comments

Comments

@mounikakandagadda29
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • 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 comments along the lines of "+1", "me too" or "any updates", 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 and review the contribution guide to help.

Description

I am trying to refer this same resource Screenshot 2024-07-05 001515 in different azurerm_sentinel_alert_rule_scheduled rule in the automation reponse block in azure sentinel.

New or Affected Resource(s)/Data Source(s)

azurerm_sentinel_automation_rule

Potential Terraform Configuration

No response

References

No response

@ziyeqf
Copy link
Contributor

ziyeqf commented Jul 8, 2024

Hi @mounikakandagadda29, thanks for opening the issue.

Could you please describe your issue with more details?

Thanks

@mounikakandagadda29
Copy link
Author

I need to reuse/refer a resource.
I have this resource created resource "azurerm_sentinel_automation_rule" "send_incident_to_soc" for sentinel automation rule and i need to use this same resource for few other rules as well.

I am unable to use the same resource, as it gives me an error saying, duplicate resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants