[Module Proposal]: avm/res/resource-graph/query

[sebassem]

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/resource-graph/query

Module Details

Submitting to help migrate from CARML

Do you want to be the owner of this module?

Yes

Module Owner's GitHub Username (handle)

sebassem

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

No response

[matebarabas]

Hi @sebassem,

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.

[sebassem]

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER Seif Bassem Sr Cloud Solution Architect - Azure Core Tech strategy team Office: +20235315608 ***@***.******@***.***> [Microsoft Logo]

[matebarabas]

Hi @sebassem,

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 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 if available. 🙏

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.

[matebarabas]

Migrated from CARML by @sebassem - PR in review: Azure/bicep-registry-modules#657

@sebassem, for future modules, please leave a message in the comment section with a PR of your module and mention the person who helped with the initial triaging! Thanks!

[matebarabas]

@sebassem, can you please create the related -owners- and -contributors GitHub teams, so we can close this issue? Please let me know when they're available, as I would then need to add them to the corresponding parent, which then you'll have to approve. Thanks!

[sebassem]

@sebassem, can you please create the related -owners- and -contributors GitHub teams, so we can close this issue? Please let me know when they're available, as I would then need to add them to the corresponding parent, which then you'll have to approve. Thanks!

Done

[matebarabas]

Thank you! I've just added both teams to the related parent. Please let me know when you accepted the request. Thanks!

[sebassem]

Thank you! I've just added both teams to the related parent. Please let me know when you accepted the request. Thanks!

Just added them, is there anything else I need to do? Should I add my fork to those teams ?

[matebarabas]

Thank you! No need to. These teams are to manage contributions on the BRM repository. E.g., if you ever decide to bring in more contributors or a secondary owner who can help you maintain this module.

With this, you have completed all necessary steps, so I'm closing this issue. Thank you again!