Hi @psinnathurai, thanks for proposing this module! Is this something you'd be interested in contributing to? Do you by any chance even have any code for this solution already? Please let us know! Thanks!

Hi @matebarabas
This is something I would be interested in contributing. As of now I don't have any code solution ready.

Thank you, @psinnathurai, for confirming you'd be interested in contributing to this module!

In order to appropriate triage this proposal, we need to go through a couple of standard questions and also finalize its name. I'll help with these steps.
Then, we can advertise it within the Microsoft community, to find a Microsoft FTE module owner who you can then work with. Just to set your expectations: this can take a long(er) time, but we'll do everything we can to draw attention to it.

For pattern modules, we're always asking the person who proposes them to address these questions. Since you've already provided the context pretty well, I'd only like to ask you to further elaborate specifically on what resources would be part of this solution, and if possible, include a logical diagram that shows the architecture.

Thank you!

Hi @psinnathurai - Have you had chance to review the reply from @matebarabas above?

Hi @ChrisSidebotham

I just saw the answer from @matebarabas. I will create a architecture diagram in until the end of next month. (Just came back from the Holidays and need to check on few other things first.)

I have added a logical Diagram on how I would image this Pattern Module would look like.
I just did it on a example Subscription but this can be forwarded to multiple Subscriptions.

Hi @psinnathurai, thank you for getting back to us with this diagram! Just for added clarity, can you please also assign labels to the objects in the bottom resource group? Thank you!

Regarding this module's name, I'd recommend something like avm/ptn/maintenance/azure-update-manager. Would you have any other suggestions, or do you think this would make sense?

Regarding finding an FTE owner, we don't yet have an update unfortunately, but we'll have an upcoming event, where we'll try to draw more attention to those modules that don't yet have an owner. Can I please ask you if you'd like to start working on the code while we're waiting for a Microsoft FTE to volunteer?

Hi @matebarabas

I have updated the Diagram.

The name sounds fine!

Sure, I will start working on that code.

@psinnathurai, I've updated the issue's title and description with the proposed name.

The diagram still seems to miss the labels from under the bottom 3 resources in the bottom RG. Is there a chance that this gets lost in translation when you're exporting it from the tool you're using?

Now it should work :-)

@psinnathurai, have you started working on the code for this pattern? If not, I could take this over.

@akhilthomas011 unfortunately I didn't start yet. Feel free to start.
I guess it also makes sense to add Event Hub for Pre and Post Events into this Pattern

Hi @akhilthomas011,

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:

• Team Definitions & RACI
• Shared Specification (Bicep & Terraform)
• Module Support

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 @akhilthomas011,

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:

• For your module:
  • ModuleName - for naming your module
  • TelemetryIdPrefix - for your module's telemetry
• For your module's repository:
  • Repo name and folder path are defined in RepoURL
  • Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
  • Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.

Check 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

Hi @matebarabas , I don't think this pattern is indexed in the module index page. I'm not able to get the details of it.

@akhilthomas011, it's not yet. I'll update the index later today. Thanks for your patience!

A draft pattern is near to completion. I will get it reviewed once done.

Thanks for the update, @akhilthomas011! Please provide a link to the PR, once it's available. Thank you!

@matebarabas - Here is the PR: Azure/bicep-registry-modules#3771