-
Notifications
You must be signed in to change notification settings - Fork 35
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
Leverage az provider list #3707
base: master
Are you sure you want to change the base?
Conversation
Does the PR have any schema changes?Looking good! No breaking changes found. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3707 +/- ##
==========================================
+ Coverage 56.41% 56.80% +0.39%
==========================================
Files 74 74
Lines 11813 11837 +24
==========================================
+ Hits 6664 6724 +60
+ Misses 4652 4617 -35
+ Partials 497 496 -1 ☔ View full report in Codecov by Sentry. |
2081bb3
to
e3086cc
Compare
d02d06d
to
f317565
Compare
cdde558
to
33452f9
Compare
We might not have been able to build a partial schema result, so can't write any interim files for debugging.
- Use built-in `--query` option instead of needing jq installed. - Move into `versions` directory where all other version data is. - Add `defaultVersion` and `locations` fields for each resourceType.
Use existing openapi.ApiVersionToDate function
- Add new report highlighting which versions in the default lock are not listed as live. - Remove old active report which was the same data as the 'az provider list' but reformatted.
- Fall back to any version if none are live. - Add documentation comments. - Create providerSpecBuilder class to give access to global, immutable data across functions to avoid passing providerName and providerList everywhere. - Simplify filtering candidate versions. Test adding resources only if they're live
- Test prefering live versions for tracking - Combine default version tests - Move lots of default version tests into the new calculateVersionMetadata tests which are a broader test and require less mocking.
33452f9
to
ec126bd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pretty tricky to review but overall LGTM. Thanks for the nice test coverage!
Fall back to all versions if as provider list doesn't include any.
Is this in case az provider list
is wrong? If it was 100% correct, we could disregard that resource altogether, no?
My main concern is that I don't think we should merge the schema and SDKs with these changes in v2. Even if the Azure API versions are not actually live, it's still a breaking code change. And there's a small chance provider list
is wrong.
Agreed. I was also concerned about removing all these. Perhaps we should feature switch the additions removals off until V3. |
Fixes #2661
az provider list
?az provider list
doesn't include any.