[Module Proposal]: `avm/res/avs/private-cloud`

[vivalada]

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?

Resource Module

Module Name

avm/res/avs/private-cloud

Module Details

Resource module to implement and configure a private cloud. Should include options for configuring add-ons, basic AVS specific networking items, operational components like monitoring, and the standard interfaces. This will support other pattern modules that include AVS specific networking.

Do you want to be the owner of this module?

No

Module Owner's GitHub Username (handle)

No response

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

No response

[jeanchg]

Hi @vivalada ,

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.

[vivalada]

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

[jeanchg]

Hi @vivalada ,

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, once your module is ready to be published! 🙏

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.

[jeanchg]

@vivalada , thank you so much for proposing to own this new module. Note: for the module name, it needs to be avm/res/avs/private-cloud to follow the specs. Also, feel free to reach out @jchancellor-ms who's also starting to work on this module on Terraform https://github.com/Azure/Azure-Verified-Modules/issues/275

[jeanchg]

Hey @vivalada , Happy New Year! Just wanted to check back on this issue and ask how far you are with its development? Can you please share your expected timeline on publishing this module? Is there anything you need help with? ccing @jchancellor-ms as well if you had a chance to sync. Thank you!

[vivalada]

Hey @jeanchg , Happy New Year. I am working on the module, having already a basic scenario working. My plan is to have everything ready no later than the end of the month. I am already syncing with @jchancellor-ms! Thank you!

[microsoft-github-policy-service[bot]]

@vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[jeanchg]

Hi @vivalada, following up on this one, checking if you need anything, even though you're in good hands with Jon. Pls feel free to share an update on this module. Thanks!

[microsoft-github-policy-service[bot]]

@vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[matebarabas]

@vivalada, do you have any updates on this module? Thank you!

[microsoft-github-policy-service[bot]]

[!IMPORTANT] @vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.

[!NOTE] This message was posted as per ITA24.

[microsoft-github-policy-service[bot]]

[!IMPORTANT] @vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.

[!NOTE] This message was posted as per ITA24.

[microsoft-github-policy-service[bot]]

[!IMPORTANT] @vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.

[!NOTE] This message was posted as per ITA24.

[microsoft-github-policy-service[bot]]

[!IMPORTANT] @vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.

[!NOTE] This message was posted as per ITA24.

[microsoft-github-policy-service[bot]]

[!IMPORTANT] @vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.

[microsoft-github-policy-service[bot]]

[!IMPORTANT] @vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.

[microsoft-github-policy-service[bot]]

[!IMPORTANT] @vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.

[microsoft-github-policy-service[bot]]

[!IMPORTANT] @vivalada, this issue has not had any activity in the last 3 weeks. Please feel free to reach out to the AVM core team should you have any questions or need any help with the development of this module.

[!TIP] To silence this notification, provide an update every 3 weeks on the Module Proposal issue, or add the "Status: Long Term :hourglass_flowing_sand:" label.

[matebarabas]

Marking this as needs module owner due to months of inactivity.