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

[k8s-configuration] Update sourceControlConfiguration SDK Models to Track2 #3676

Merged

Conversation

jonathan-innis
Copy link
Contributor


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

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 PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

* Add check for provider registration and refactor

* Fix bug in checking registration

* Add license header to utils

* Update private key check and error messaging

* Update based on refactoring

* Fix failing tests

* Add provider registration check

* Create a test for uppercase url, address comments

* Add blank line to fix style check
* Update models to track2

* Increase k8s-configuration version number

* Update kind version

* Change error to warning because of DSA failure
@jonathan-innis jonathan-innis force-pushed the k8s-configuration-release-1.1.0 branch from c26cd0f to 9722b66 Compare July 20, 2021 20:18
@yonzhan yonzhan requested review from zhoxing-ms and jsntcy July 20, 2021 23:25
@yonzhan yonzhan added this to the Jul 2021 (2021-08-03) milestone Jul 20, 2021
@yonzhan
Copy link
Collaborator

yonzhan commented Jul 20, 2021

k8s-configuration

@zhoxing-ms
Copy link
Contributor

Could you run some live tests for these changes?

@jonathan-innis
Copy link
Contributor Author

Could you run some live tests for these changes?

What kind of live tests are you looking for? We have had issue with live tests previously because we require an AKS cluster and connected cluster to be pre-provisioned in order to run tests against it

@zhoxing-ms
Copy link
Contributor

What kind of live tests are you looking for? We have had issue with live tests previously because we require an AKS cluster and connected cluster to be pre-provisioned in order to run tests against it

OK, I see. I also would like to ask can all the tests cover these changes, and have you rerun those tests in record mode?

@jonathan-innis
Copy link
Contributor Author

Record mode is difficult to run as well because some of these resources take identity which is not repeatable in record mode. We have an E2E test suite that we run on our end that covers all cases

@zhoxing-ms
Copy link
Contributor

OK, it is suggested to fix those issues related tests in live mode/record mode in the future, so that our pipeline can better maintain and test the code quality

@zhoxing-ms zhoxing-ms merged commit e298f57 into Azure:main Jul 23, 2021
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.

5 participants