[Orphaned Module]: `avm/res/communication/email-service`
krbar opened this issue · comments
Bicep or Terraform?
Bicep
Module Classification?
Resource Module
Module Name
avm/res/communication/email-service
Module Details
This is an "Orphaned Module" issue to change the ownership of the avm/res/communication/email-service
module to @donk-msft, which has been agreed with him.
Do you want to be the new owner of this module?
No
Module Owner's GitHub Username (handle)
donk-msft
(Optional) Secondary Module Owner's GitHub Username (handle)
No response
Hi @donk-msft,
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
#RR
I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER
Hi @donk-msft,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
We just want to ask you to double check a few important things.
Please use the following values explicitly as provided in the module index page:
- You must be the owner of the GitHub teams as outlined here.
- Please check that your name has been updated in the module index page (this should happen shortly after you confirmed ownership).
You can now take ownership of this module and start improving it as needed! ✅ Happy coding! 🎉
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team
@krbar, have the related GH teams already been handed over to @donk-msft? Thanks!
@matebarabas The GH-Teams are transferred to @donk-msft
Thanks for confirming, @krbar! I'm closing this issue now.