Skip to content

Conversation

@bavneetsingh16
Copy link
Contributor


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

Related command

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.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Miraj50 and others added 30 commits September 29, 2022 13:17
* First draft for Data Protection K8s backup extension (Pending internal review)

* Removing tracing

* Minor changes to improve azdev style

* Internal PR review feedback

Co-authored-by: Rishabh Raj <[email protected]>
…ad of workspace (#175)

* fix: Update DCR creation to Clusters resource group instead of workspace

* .

* .

* casing check
adding the api version to the operation definition in the client factory
…tests

adding tests for all 4 extension types calls
…tensiontypetests

adding upstream test for extension types
…eate (#188)

* Add more validations and user prompt for existing installation scenario

Signed-off-by: Shubham Sharma <[email protected]>

* Add Dapr test'

Signed-off-by: Shubham Sharma <[email protected]>

* Handle stateful set

Signed-off-by: Shubham Sharma <[email protected]>

* Update default handling

Signed-off-by: Shubham Sharma <[email protected]>

* Fix HA handling

Signed-off-by: Shubham Sharma <[email protected]>

* Add placement service todo

Signed-off-by: Shubham Sharma <[email protected]>

* Add non-interactive mode

Signed-off-by: Shubham Sharma <[email protected]>

* Fix lint

Signed-off-by: Shubham Sharma <[email protected]>

* Update tests

Signed-off-by: Shubham Sharma <[email protected]>

* Reset configuration for StatefulSet during k8s upgrade

Signed-off-by: Shubham Sharma <[email protected]>

* Fix lint

Signed-off-by: Shubham Sharma <[email protected]>

* Retrigger tests

Signed-off-by: Shubham Sharma <[email protected]>

* Add changes to manage ha and placement params

Signed-off-by: Shubham Sharma <[email protected]>

* Update message

Signed-off-by: Shubham Sharma <[email protected]>

* nits

Signed-off-by: Shubham Sharma <[email protected]>

Signed-off-by: Shubham Sharma <[email protected]>
@azure-client-tools-bot-prd
Copy link

azure-client-tools-bot-prd bot commented Jul 28, 2023

️✔️Azure CLI Extensions Breaking Change Test
️✔️Non Breaking Changes

@azure-client-tools-bot-prd
Copy link

Hi @bavneetsingh16,
Since the current milestone time is less than 7 days, this pr will be reviewed in the next milestone.

@yonzhan
Copy link
Collaborator

yonzhan commented Jul 28, 2023

k8s-extension

Comment on lines +207 to +208
return VersionInfo.parse(v1) < VersionInfo.parse(v2)
except ValueError:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May I ask why do you need to use semver instead of packaging?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The reason is mentioned in AzureArcForKubernetes#241. Please let me know if you need more information.

@jiasli
Copy link
Member

jiasli commented Aug 4, 2023

Approving for the usage of semver part.

BTW, there are 85 commits in this PR. It's better to rebase it to main and clean up the history.

@zhoxing-ms
Copy link
Contributor

BTW, there are 85 commits in this PR. It's better to rebase it to main and clean up the history.

@bavneetsingh16 Please help rebase the code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Auto-Assign Auto assign by bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.