feat: Add new ptn modules azd/apim-api

[jianingwang123]

Description

Fixes Azure/Azure-Verified-Modules/issues#1232

Pipeline Reference

Pipeline

Type of Change

• Update to CI Environment or utilities (Non-module affecting changes)
• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
    • The bug was found by the module author, and no one has opened an issue to report it yet.
  • 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

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

@jongio for notification.

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[microsoft-github-policy-service]

Important

If this is a module-related PR, being submitted by the sole owner of the module, the AVM core team must review and approve it (as module owners can't approve their own PRs).

To indicate this PR needs the core team''s attention, apply the "Needs: Core Team 🧞" label!

The core team will only review and approve PRs that have this label applied!

[matebarabas]

@AlexanderSehr, @jianingwang123, good news: the MAR manifest has been updated with the required record(s) for this module. You can take the next steps accordingly. Thanks.

[matebarabas]

@jianingwang123, please make sure the following disclaimer is added to the readme.md of this module - preferably somewhere close to the top: "This module is not intended for broad, generic use, as it was designed to cater for the requirements of the AZD CLI product. Feature requests and bug fix requests are welcome if they support the development of the AZD CLI but may not be incorporated if they aim to make this module more generic than what it needs to be for its primary use case."

[v-xuto]

@AlexanderSehr Could you help review this PR?

[AlexanderSehr]

Hey @jianingwang123,
just one small other comment. Otherwise it appears we're good to go. The only other thing that needs fixing are the conflicts 💪

[jianingwang123]

@AlexanderSehr I have updated based on your comments, please re-review.

[AlexanderSehr]

Hey @jianingwang123,
please note that the module publishing failed because the static test failed. As per the error, it seems the generated files where to up to date when merging the PR.
To solve this we need a few things:

1. You need to create a new PR based on the latest code in main
2. In that PR you need to introduce a change to the main.json file. It does not matter what it is (e.g., it can be a change to the module's description or a parameter), but it must be something that tells the CI 'hey something that justifies a new module version changed'
3. You need to run the Set-AVMModule script again to make sure the files are up to date
4. You ideally also run the pipeline again so that we can ensure the tests wont' fail again

[jianingwang123]

Hey @jianingwang123, please note that the module publishing failed because the static test failed. As per the error, it seems the generated files where to up to date when merging the PR. To solve this we need a few things:

1. You need to create a new PR based on the latest code in main
2. In that PR you need to introduce a change to the main.json file. It does not matter what it is (e.g., it can be a change to the module's description or a parameter), but it must be something that tells the CI 'hey something that justifies a new module version changed'
3. You need to run the Set-AVMModule script again to make sure the files are up to date
4. You ideally also run the pipeline again so that we can ensure the tests wont' fail again

@AlexanderSehr The PR for it is ready. Please help review.