azure-powershell icon indicating copy to clipboard operation
azure-powershell copied to clipboard

[Resources] powershell for export as bicep

Open anamikapan opened this issue 11 months ago • 10 comments

Description

Mandatory Checklist

  • Please choose the target release of Azure PowerShell. (⚠️Target release is a different concept from API readiness. Please click below links for details.)

    • [ ] General release
    • [ ] Public preview
    • [ ] Private preview
    • [ ] Engineering build
    • [ ] No need for a release
  • [ ] Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

  • SHOULD update ChangeLog.md file(s) appropriately
    • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
      • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
    • For autorest-based development mode, include the changelog in the PR description.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
  • SHOULD have proper test coverage for changes in pull request.
  • SHOULD NOT adjust version of module manually in pull request

anamikapan avatar Mar 06 '25 20:03 anamikapan

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

/azp run

notyashhh avatar Mar 08 '25 13:03 notyashhh

Azure Pipelines successfully started running 3 pipeline(s).

azure-pipelines[bot] avatar Mar 08 '25 13:03 azure-pipelines[bot]

Hey @anamikapan, please add some description to the PR. There are a few steps required from your side before I can review it,

  1. SHOULD regenerate markdown help files if there is cmdlet API change. Instruction

  2. SHOULD update ChangeLog.md file(s) appropriately

  • For SDK-based development mode, update src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense.
  • For autorest-based development mode, include the changelog in the PR description. Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  1. Please fill out the mandatory checklist in this PR.

Please reach out if any help is required from our side 😄

notyashhh avatar Mar 08 '25 13:03 notyashhh

This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.

github-actions[bot] avatar Mar 08 '25 13:03 github-actions[bot]

Hi @anamikapan , gently ping, is there any update to @notyashhh 's comment?

wyunchi-ms avatar May 06 '25 07:05 wyunchi-ms

/azp run

msJinLei avatar May 20 '25 02:05 msJinLei

Azure Pipelines successfully started running 3 pipeline(s).

azure-pipelines[bot] avatar May 20 '25 02:05 azure-pipelines[bot]

Hi @anamikapan if you are not working on the PR recently, we are going to close it. You can reopen it when you want to continue your job.

msJinLei avatar May 20 '25 02:05 msJinLei

@anamikapan I am converting this PR as draft since it has no progress for long. You can convert it back once you are ready to work on it. Thanks for your contribution!

vidai-msft avatar May 27 '25 05:05 vidai-msft

OLD stale PR close it

anamikapan avatar Jun 30 '25 19:06 anamikapan

old PR

anamikapan avatar Jun 30 '25 19:06 anamikapan