[Module Proposal]: avm-res-servicenetworking-trafficcontroller (tf)

[shailwx]

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?

Terraform

Module Classification?

Resource Module

Module Name

avm-res-servicenetworking-trafficcontroller

Module Details

Application Gateway for Containers (Traffic Controller)

Do you want to be the owner of this module?

Yes

Module Owner's GitHub Username (handle)

shailwx

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

No response

[mbilalamjad]

Hi @shailwx thank you for the module proposal, a couple of observations.

1. Module name should be following the naming pattern appreciate if you could update it accordingly for us to triage the proposal
2. This might be covered already in the application gateway module being developed.
3. In case you believe the above point isn't true and this needs to exist as a separate module than we would need to find a Microsoft FTE as the owner as that is a requirement for AVM

[prjelesi]

@shailwx Thanks for proposing. We will search for MSFT FTE to own module. Would you like to contribute to development of this module?

[shailwx]

@prjelesi, sure no problem. Yes I would like to contribute to the development of this module

[mofaizal]

The service become GA last week, we should include part of avm-res-network-applicationgateway I don't we need to separate module for this.

[prjelesi]

@mofaizal this should be different resource type. Pls correct me if I am wrong?

[mofaizal]

Yes, and agree. I notice this is fall under different resource tree, I thought this is part of networking, but this is fall under Service Networking. We should have different TF module for this.

[prjelesi]

Thanks @mofaizal ,

Since you mention that you are open to own this module:

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

[matebarabas]

@prjelesi, please note the related Bicep issue (I linked above): #712. The module name should be aligned with the Bicep equivalent. Please update this issue's name and its description to reflect this too. Thanks!

[microsoft-github-policy-service]

Note

The "Needs: Author Feedback 👂" label was removed and the "Needs: Attention 👋" label was added as per ITA11.

[mofaizal]

@prjelesi Thanks and "I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"

[prjelesi]

@mofaizal , @shailwx module name is updated,

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

[shailwx]

Thanks @prjelesi, @mofaizal

@mofaizal , should we setup our first meeting to get started on this ?

[matebarabas]

@mofaizal, I just pinged you via Teams internally. Please continue by setting up a Teams call with @shailwx - I've shared all details. Thank you!

[mofaizal]

@prjelesi and @matebarabas I had a teams meeting with @shailwx on this TF module. Created private repo and given access to @shailwx to develop module.

https://github.com/Azure/avm-res-servicenetworking-trafficcontroller

@shailwx. Thanks for your support and helping us. Let me know when you are ready happy to jump on call to take a look.

[microsoft-github-policy-service]

Important

@mofaizal, 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 ⏳" label.

Note

This message was posted as per ITA24.

[microsoft-github-policy-service]

Important

@mofaizal, 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 ⏳" label.

[mofaizal]

@prjelesi Thanks for the follow up, i setup a repo and got deleted due to internal policy. Will setup again

[microsoft-github-policy-service]

Important

@mofaizal, 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 ⏳" label.

[mofaizal]

Back from vacation will look into this and update soon

[microsoft-github-policy-service]

Important

@mofaizal, 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 ⏳" label.

[microsoft-github-policy-service]

Important

@mofaizal, 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 ⏳" label.

[microsoft-github-policy-service]

Important

@mofaizal, 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 ⏳" label.

[microsoft-github-policy-service]

Important

@mofaizal, 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 ⏳" label.