Open bzabber opened 4 months ago
Hi @bzabber
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:
Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER
@bzabber i will ping you offline to clarify something.
Hi @bzabber ,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:
ModuleName
- for naming your moduleTelemetryIdPrefix
- for your module's telemetryCheck if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team
@prjelesi Noticed that the module name in the For Module Owners & Contributors is doesn't align with the name of the resource and also doesn't align with its Bicep AVM counterpart. The module name should be "avm-res-insights-scheduledqueryrule". I've created the repo with the proper spelling, can you update your end?
[!IMPORTANT] @bzabber, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.
[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.
@prjelesi Can you update the documentation for the modules as referenced in my previous comment? Please reach out if you have any questions or concerns.
[!IMPORTANT] @bzabber, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.
[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.
[!IMPORTANT] @bzabber, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.
[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.
I had a discussion with Bryan and Joseph. Going forward Joseph Barnes would be the new owner for this issue and Bryan would continue to contribute as external contributor. Thank you @bzabber for all the work & please continue to contribute.
[!IMPORTANT] @bzabber, @JoeyBarnes, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.
[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.
Check for previous/existing GitHub issues/module proposals
Check this module doesn't already exist in the module indexes
Bicep or Terraform?
Terraform
Module Classification?
Resource Module
Module Name
avm-res-insights-scheduledqueryrule
Module Details
A way to create Azure Monitor Log alerts (scheduled query alerts v2) using Terraform. It will reference an existing Azure Monitor Log Analytics workspace.
Do you want to be the owner of this module?
Yes
Module Owner's GitHub Username (handle)
bzabber
(Optional) Secondary Module Owner's GitHub Username (handle)
JoeyBarnes