[Module Proposal]: `avm/ptn/lza-shared/data-services`

[kpantos]

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; or I'm proposing the module to be migrated from CARML/TFVM.

Bicep or Terraform?

Bicep

Module Classification?

Pattern Module

Module Name

avm/ptn/lza-shared/data-services

Module Details

This LZA data-services pattern module represents a common data services deployment for a LZA architecture 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 data-services pattern module deploys several commonly used Azure data services for all the LZA pattern modules.

Do you want to be the owner of this module?

Yes

Module Owner's GitHub Username (handle)

kpantos

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

No response

[matebarabas]

@kpantos, thank you for proposing this module! As this is categorized as a pattern module, its approval will require a more thorough assessment. The AVM core team will get back to you soon. Thank you for your patience!

[kpantos]

@matebarabas why is this proposal at looking for owner state? I've already selected that I want to own the pattern module.

[matebarabas]

@kpantos, I'll reach out to you internally regarding this proposal and the other 2 that you filed along with it.

To your question: I'm not sure why @eriqua has changed the status of this, but we'll properly administer everything on this issue once we aligned internally.

[eriqua]

My bad @kpantos, that was definitely unintended.

[matebarabas]

This module will take a dependency on https://github.com/Azure/Azure-Verified-Modules/issues/604.

[matebarabas]

Hi @kpantos,

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

[kpantos]

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

[matebarabas]

Hi @kpantos,

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

[matebarabas]

@kpantos, thanks again for proposing this module! Please don't forget to add the discussed details to the description, including the architectural diagram, and bill of materials. Thanks!

[matebarabas]

@kpantos, I just pinged you internally regarding the inactivity on this module's development. Please let me know how you're planning to proceed. Thanks!

[kpantos]

@matebarabas after having several internal alignment discussions with the whole Tech Strategy team we need to change the naming of the proposed pattern module from avm/ptn/aca-lza/data-services to avm/ptn/lza/data-services, as this module is going to be common across all our LZAs products and not just the aca one. Can you please assist us on how to go about this?

[matebarabas]

As agreed, this module will be renamed from avm/ptn/aca-lza/data-services to avm/ptn/lza-shared/data-services. This way, smaller sections of more complex LZA modules that can be reused across multiple LZA pattern modules can be placed into the lza-shared folder.

Steps for renaming this module:

• [x] 1. Update the AVM module proposal (this issue) with the new module name - @matebarabas
• [x] 2. Update BRM PR (if already available) with the new module name (rename folder structure, update to new telemetry ID prefix, update readme as needed, etc.) - @kpantos --> no action needed, as it hasn't been submitted yet
• [x] 3. Update the module index with the new name - @matebarabas
• [x] 4. Submit a PR to update the MAR manifest file with the new name - @matebarabas
• [x] 5. MAR manifest PR merge confirmed - @matebarabas
• [x] 6. Update GitHub team names - @kpantos --> no action needed, as it hasn't been submitted yet

Note: these don't necessarily have to be performed in this exact order, but all of them need to be confirmed before the code can be merged under the new name.

[matebarabas]

@kpantos, all requirements listed above are now complete.

[kpantos]

Thank you @matebarabas really appreciate it. Will start working on this asap.