[Module Proposal]: avm/res/network/trafficmanagerprofile

[lsnoddy]

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 another project that is being evolved into AVM

• I have checked for that this module doesn't already exist in CARML or TFVM

Terraform or Bicep?

Bicep

Module Classification?

Resource Module

Module Name

avm/res/network/trafficmanagerprofile

Module Details

Migrate existing module from CARML

Do you want to be the owner of this module?

Yes

Module Owner's GitHub Username

lsnoddy

[matebarabas]

Hi @lsnoddy,

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

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.

[lsnoddy]

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

[matebarabas]

Hi @lsnoddy,

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 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

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]

Please also note that since this is a migrate from CARML scenario, @prjelesi might be able to help you with the next steps. Please feel free to contact him internally.

[matebarabas]

@lsnoddy,

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.

[microsoft-github-policy-service]

@@lsnoddy, 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.

[lsnoddy]

Pull request has been submitted: (Azure/bicep-registry-modules#699)

[matebarabas]

@lsnoddy, I've just noticed that this PR has already been merged. Next time, please drop a note here for faster processing! Thanks! 😉

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

Thank you for your work! I'm closing this issue now.