[Module Proposal]: avm/res/insights/private-link-scope

[ahmadabdalla]

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/insights/private-link-scope

Module Details

Migration from CARML
https://github.com/ahmadabdalla/bicep-registry-modules/tree/users/ahmad/4413_privateLinkScopes

Do you want to be the owner of this module?

Yes

Module Owner's GitHub Username (handle)

ahmadabdalla

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

No response

[matebarabas]

Hi @ahmadabdalla,

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

[ahmadabdalla]

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

[matebarabas]

Hi @ahmadabdalla,

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

[microsoft-github-policy-service]

@ahmadabdalla, 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]

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

Thank you for your work @ahmadabdalla!