[Module Proposal]: `avm/res/digital-twins/digital-twins-instance`

[ChrisSidebotham]

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/digital-twins/digital-twins-instance

Module Details

Migrate from CARML to BRM

Do you want to be the owner of this module?

No

Module Owner's GitHub Username (handle)

ryanmstephens

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

No Response

[jeanchg]

@ChrisSidebotham, thanks for creating this module proposal. I'll send you a request to confirm ownership right after (you know the process already but it's just to be consistent with all module proposals). Thanks for all your contributions!

[jeanchg]

Hi @ChrisSidebotham,

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

[ChrisSidebotham]

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

[matebarabas]

Hi @ChrisSidebotham,

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.

[matebarabas]

@ChrisSidebotham,

Due to a recent change in the naming convention for AVM Bicep modules, this module is getting an updated name.

The title and description of this GH issue has been updated to reflect the name change. Please make sure you adhere to the new naming convention when publishing your module!

Please see the new naming convention in:

• RMNFR1 for resource modules
• PMNFR1 for pattern modules

Please note that the Telemetry ID and name of GitHub Teams haven't changed.

If you feel uncertain about any details, please check the Bicep modules indexes.

[ChrisSidebotham]

@ryanmstephens - Let's catch up on this

[ChrisSidebotham]

Delayed till 2024

[matebarabas]

@ChrisSidebotham, I just would like to check back on the expected timeline: when do you think this could be done by? Are you actively working on this? Is there a blocker/dependency? Thanks!

CC: @jeanchg

[ChrisSidebotham]

@ryanmstephens - Any idea when you might get to this? I can migrate the module if you are happy to support it for any issues that are opened :)

[matebarabas]

Reopening. @ChrisSidebotham, I just spoke with @ryanmstephens internally and we concluded that it'd be great if you could please help with the migration and then Ryan could take care of the rest of the module's lifecycle. Can you please help with this one? Thanks!

[ChrisSidebotham]

Initial Import started....

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

@ChrisSidebotham, @ryanmstephens, 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]

@ryanmstephens, @ChrisSidebotham, can you please share any updates on this one? Thanks!

[matebarabas]

• [x] Module published. PR: https://github.com/Azure/bicep-registry-modules/pull/1277
• [x] GitHub teams are available and assigned to their parents.
  • The avm-res-digitaltwins-digitaltwinsinstance-module-contributors-bicep team exists but is hasn't been assigned to its respective parent team: avm-module-contributors-bicep.
• [x] CODEOWNERS file updated.

Thank you for your work @ChrisSidebotham! Please let me know when the missing team relationship is fixed, so I can close this issue.

[ChrisSidebotham]

This is now updated and completed @matebarabas

[matebarabas]

Thanks for confirming, I'm closing this issue now.

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

[!NOTE] The "Status: In PR :point_right:" label was removed as per ITA23.