-
Notifications
You must be signed in to change notification settings - Fork 53
json-schema-refactoring #3939
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
json-schema-refactoring #3939
Conversation
0eb356a to
300eaca
Compare
d1d1552 to
0634a3e
Compare
9930f88 to
f102249
Compare
76f181c to
cb8652f
Compare
|
Added not-merge-lable to align on the release this should go in. |
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.
LGTM, with two main points:
- Since we decided not to bring in a second binding schema for now, I would suggest not renaming the current schema to
legacyto not cause confusion. - If possible not duplicate the binding schema definition in two places. As it is not exported I think it can stay where it currently is without a copy in
schema/.
Co-authored-by: Silvestre Zabala <[email protected]>
Co-authored-by: Silvestre Zabala <[email protected]>
|
File-renamings done! |
src/autoscaler/api/publicapiserver/publicapiserver_suite_test.go
Outdated
Show resolved
Hide resolved
6393018 to
8178d7d
Compare
|
All tests are green now and reviewer approval is there. I now remove the todo-item from templates/app-autoscaler.yml. |
|



This PR contains the following changes:
app-guidwhich is a prerequisite to support service-keys.