Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Site-Recovery] GA Release #5349

Merged
merged 105 commits into from
Aug 29, 2023
Merged

[Site-Recovery] GA Release #5349

merged 105 commits into from
Aug 29, 2023

Conversation

calvinhzy
Copy link
Member

@calvinhzy calvinhzy commented Sep 14, 2022


This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

Fix Azure/azure-cli#22631

General Guidelines

  • Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
  • Have you run python scripts/ci/test_index.py -q locally?

For new extensions:

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

@yonzhan
Copy link
Collaborator

yonzhan commented Sep 14, 2022

Site-Recovery

@calvinhzy calvinhzy changed the title [Site-Recovery] [Site-Recovery] GA Release Aug 11, 2023
@calvinhzy calvinhzy marked this pull request as ready for review August 29, 2023 03:41
@necusjz necusjz merged commit 4478e80 into Azure:main Aug 29, 2023
@azclibot
Copy link
Collaborator

[Release] Update index.json for extension [ site-recovery ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=86691&view=results

bgashirabake pushed a commit to bgashirabake/azure-cli-extensions that referenced this pull request Aug 30, 2023
* init site-recovery

* actual init with all commands

* shorten args

* shorten args

* shorten

* use latest aaz version

* test up to alert-setting

* fix some comments

* fix delete and add some more tests(not fully working)

* vault policy tests

* rerun

* move fabric command group to top level

* change name

* stuck on fabric

* rerun test

* add examples

* restructure commands

* rename --resource-name to --vault-name

* move protection-container-mapping to top level

* fix delete protection-container-mapping

* add more testing, not fully working

* move protected-item to top level

* change a2-a to a2a

* fix delete network mapping

* a2-a to a2a

* a2-a to a2a

* tested up to commit unplanned failover

* remove protection container fix

* move network-mapping to under fabric instead of network

* change protection-container-mapping to fabric protection-container mapping

* works up to recovery-plan a2a

* fix delete recoveryplan

* finish A2A testing

* added partial testing

* add HyperVSite to create fabric type

* add HyperVSite to create container mapping type

* container mapping works

* use hard coded values

* enable protection works

* use aaz-dev-tool 0.20.0

* add some more examples

* add some more examples

* failback still fails

* remove untested commands

* rerun tests

* add more examples

* add more examples

* add back commands

* add back commands

* remove commands

* add fabric remove

* add test with a2a self created resources

* remove some unfinished tests

* make test record only

* make test record only

* service_name

* add readme instructions

* add examples

* record only

* record only recording

* remove partially complete tests

* remove {} in examples

* recording

* live test takes 2 hrs so record only

* add back tests for full release

* regen with list pagination

* add back protectable-item list/show

* partial testing

* add vmmtoazure for network mapping create

* move protectable-item to top level

* move network-mapping to top level

* move protection-container to top level

* move policy to top level

* move alert-setting to top level

* update readme based on cmd renames

* move event/job/recovery-plan to top level

* add logical-network and network, move network-mapping to network mapping

* test before enable protection done

* test b2a up to enable protection

* add `protected-item planned-failover`, not working yet

* fix some param names

* testing H2A B2A case done

* add h2a b2a examples

* updated e2a test(not passed yet), deleted b2a service generated test case

* E2A test passed

* container mapping for v2arcm

* add some examples

* add recovery-services-provider list in fabric

* add vmware-site machine list

* add vmware-site run-as-account list

* add to arg options list

* add protected-item reprotect

* tested up to reprotect for v2arcm case

* v2arcm case recorded

* need to fix test for recording

* record only

* add example for v2arcm case

* remove v2a cs cases as will be deprecated in the future hide v2a classic stack (CS) params

* rerun test

* update version info

* record only

* param help
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Terraform and CLI work for GA of Site Recovery: V2ARCM
4 participants