feat: Deprecating module Microsoft.Network/frontDoors

[hundredacres]

Description

Deprecating module.

Pipeline Reference

Pipeline

Type of Change

• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation
• Update to CI Environment or utilities (Non-module affecting changes)

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• I have run Set-AVMModule locally to generate the supporting module files.
• My corresponding pipelines / checks run clean and green without any errors or warnings
• I have updated the module's CHANGELOG.md file with an entry for the next version

[AlexanderSehr]

I think there are 3 more TODOs:

1. Remove the workflow file (it will fail now anyways)
2. Remove the entry from the issue template & CODEOWNERS
3. Remove the Teams

Thoughts, @matebarabas ?

[hundredacres]

@AlexanderSehr @matebarabas the docs indicate a 2 PR process, where the additional items (remove the workflow file, etc.) are done in the 2nd PR.

[AlexanderSehr]

@AlexanderSehr @matebarabas the docs indicate a 2 PR process, where the additional items (remove the workflow file, etc.) are done in the 2nd PR.

Hey @hundredacres,
you're correct. We merged these guidelines in just the other day and had another meeting about it today. There's a fair chance we'll simplify the process to on PR that takes care of it all, as publishing a new version of the module just to get the 'deprecated' note into the description seems to be a bit of a overkill if you ask me 😄 . We'll settle this latest this Thursday and can then resolve this accordingly.

[AlexanderSehr]

Hey @hundredacres,
the PR with the updated guidelines just went in.
Just a few more things left to do

• Add the statement NOTE: This is the last published version and the module has since been deprecated. to the top-most entry of the CHANGELOG.md ### Changes header
• Remove the module's workflow
• Remove the module from the Github issue template (avm_module_issue.yml)
• Remove the module from the CODEOWNERS file (CODEOWNERS)
• Undo the change to the version.json file. We won't publish another version for the deprecation
• Delete the module's Contributor & Owner teams

[hundredacres]

@AlexanderSehr completed the remaining steps

[ReneHezser]

LGTM

[karpikpl]

module shows as active in AVM catalog

[matebarabas]

@karpikpl, this PR will update the status to deprecated. Thanks for calling this out!