Azure / Azure-Verified-Modules

Azure Verified Modules (AVM) is an initiative to consolidate and set the standards for what a good Infrastructure-as-Code module looks like. Modules will then align to these standards, across languages (Bicep, Terraform etc.) and will then be classified as AVMs and available from their respective language specific registries.
https://aka.ms/AVM
MIT License
321 stars 68 forks source link

[Module Proposal]: `avm/ptn/data/private-analytical-workspace` #949

Open jbinko opened 4 months ago

jbinko commented 4 months ago

Check for previous/existing GitHub issues/module proposals

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

Bicep or Terraform?

Bicep

Module Classification?

Pattern Module

Module Name

avm/ptn/data/private-analytical-workspace

Module Details

This pattern module aims to provide a set of Azure services that work Together often for data analytics workloads. It helps Azure customers in highly regulated industries deploy such a set faster with high security and privacy. Most services should not use public IP and should go through HUB, spoke, and firewall. This is common in healthcare and finance. I have used this pattern many times and want to make it part of the AVM + follow AVM specs + refresh to the latest features. I posted this pattern in in the past in the Azure repo for my customers to use. This is based on practical experience with customers and practical requirements in the industry. https://github.com/Azure/ADAW

Alt text

Do you want to be the owner of this module?

Yes

Module Owner's GitHub Username (handle)

jbinko

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

No response

matebarabas commented 4 months ago

Hi @jbinko, thanks for proposing and volunteering to own this module! I've pinged you internally to clarify a few questions before proceeding with the triage of this module.

matebarabas commented 4 months ago

Hi @jbinko,

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

jbinko commented 4 months ago

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

matebarabas commented 3 months ago

Hi @jbinko,

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:

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

jbinko commented 3 months ago

Here is the fork and branch where the development is in the progress: https://github.com/jbinko/bicep-registry-modules/tree/private-analytical-workspace/avm/ptn/data/private-analytical-workspace

jbinko commented 2 months ago

Note for bot: Work in progress

jbinko commented 15 hours ago

The initial version 0.1 implementation is complete, and a pull request has been submitted. This includes documentation, unit tests, and PowerShell post-unit tests.

https://github.com/Azure/bicep-registry-modules/pull/3307