ibersanoMS commented 1 month ago

Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

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

[X] I have checked for that this module doesn't already exist in the module indexes.

Bicep or Terraform?

Bicep

Module Classification?

Pattern Module

Module Name

avm/ptn/app-service-lza/hosting-environment

Module Details

This Azure App Service pattern module represents an Azure App Service deployment aligned with the cloud adoption framework implementing industry proven practices, such as those presented in Azure landing zones guidance in the Cloud Adoption Framework, owned and operated by a workload team. This AVM pattern module provides a production ready reference implementation of a hosting an application on App Service. App Service LZA AVM Pattern .

Deployment of the hub is optional and will be included as one of the test scenarios.

This module deploys the following services:

A resource group to deploy all the spoke resources
A VNET with four subnets
An Azure App Service Premium Plan
An App Service
An Azure key vault exposed through a private endpoint
An Azure Container Registry exposed through a private endpoint
Azure Front Door to expose applications hosted on Azure App Service
A Virtual Machine serving as a jump box for the environment

Do you want to be the owner of this module?

Yes

Module Owner's GitHub Username (handle)

ibersanoMS

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

No response

matebarabas commented 1 month ago

Hi @ibersanoMS,

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

ibersanoMS commented 1 month ago

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

matebarabas commented 1 month ago

Hi @ibersanoMS,

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!