[Module Proposal]: avm/res/network/application-gateway (bicep)

[ilhaan]

Check for previous/existing GitHub issues/module proposals

• I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

• I have checked for that this module doesn't already exist in the module indexes; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?

Bicep

Module Classification?

Resource Module

Module Name

avm/res/network/application-gateway

Module Details

Module that deploys Azure Application Gateway resource

Do you want to be the owner of this module?

Yes

Module Owner's GitHub Username (handle)

ilhaan

(Optional) Secondary Module Owner's GitHub Username (handle)

No response

[matebarabas]

Hi @ilhaan,

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

NOTE:

• This Module Proposal issue MUST remain open until the module is fully developed, tested and published to the relevant registry. Do NOT close the issue before the successful publication is confirmed!
• Once the module is fully developed, tested and published to the relevant registry, and the Module Proposal issue was closed, it MUST remain closed.

[ilhaan]

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER

[matebarabas]

Hi @ilhaan,

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 and take the next steps before you start the development.

Please use the following values explicitly as provided in the module index page:

• For your module:
  • ModuleName - to name your module
  • TelemetryIdPrefix - to be used in your module's telemetry
• For your module's repository:
  • Repository name and folder path are defined in RepoURL
  • Create the GitHub teams defined in the ModuleOwnersGHTeam and ModuleContributorsGHTeam columns and grant them permissions as described here.
    • In case of a Bicep module, please let the AVM core team know when you created these teams, and we'll help you with assigning the necessary permissions as described here.
    • In case of a Terraform module, follow the instructions here and assign the necessary permissions.

Grant the right level of permissions for the AVM core team and PG teams on your GitHub repo as described here.

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 if available. 🙏

Any further questions or clarifications needed, let us know!

Thanks,

The AVM Core Team

NOTE:

• This Module Proposal issue MUST remain open until the module is fully developed, tested and published to the relevant registry. Do NOT close the issue before the successful publication is confirmed!
• Once the module is fully developed, tested and published to the relevant registry, and the Module Proposal issue was closed, it MUST remain closed.

[matebarabas]

ilhaan,

Due to a recent change in the naming convention for AVM Bicep modules, this module is getting an updated name.

The title and description of this GH issue has been updated to reflect the name change. Please make sure you adhere to the new naming convention when publishing your module!

Please see the new naming convention in:

• RMNFR1 for resource modules
• PMNFR1 for pattern modules

Please note that the Telemetry ID and name of GitHub Teams haven't changed.

If you feel uncertain about any details, please check the Bicep modules indexes.

[ilhaan]

Thanks @matebarabas. GitHub Teams created:

• https://github.com/orgs/Azure/teams/avm-res-network-applicationgateway-module-owners-bicep
• https://github.com/orgs/Azure/teams/avm-res-network-applicationgateway-module-contributors-bicep

[matebarabas]

I've just requested the -owners- team to be added to the -technical-reviewers- team. Please approve.

[ilhaan]

@matebarabas approved

[matebarabas]

@ilhaan, I just would like to check back on this issue and ask how far do you think you are? Can you please share your expected timeline on publishing this module? Is there anything you need help with?

Thank you!

CC: @jeanchg

[ilhaan]

@matebarabas I should be able to send out an initial PR by the end of next week.

[matebarabas]

That's great news, thanks for the update!

[matebarabas]

Draft PR: Azure/bicep-registry-modules#835

[ilhaan]

Still working on this

[ilhaan]

Still working on this

[ilhaan]

Still working on this. Draft PR here: Azure/bicep-registry-modules#835

[ilhaan]

PR ready for review: Azure/bicep-registry-modules#835

[matebarabas]

• Module published.
• GitHub teams are available and assigned to their parents.
• CODEOWNERS file updated.

Thank you for your work @ilhaan! I'm closing this issue now.