Skip to content

API change for v6.0.0b1#477

Merged
mbohlool merged 2 commits into
kubernetes-client:masterfrom
roycaihw:apichange-6.0
Mar 9, 2018
Merged

API change for v6.0.0b1#477
mbohlool merged 2 commits into
kubernetes-client:masterfrom
roycaihw:apichange-6.0

Conversation

@roycaihw

@roycaihw roycaihw commented Mar 9, 2018

Copy link
Copy Markdown
Member

Committing generated API change for v6.0.0b1:

  • add PATCH to custom_objects_api
  • documentation update: never let cluster-scoped resources skip webhooks

also updating README and CHANGELOG

roycaihw added 2 commits March 9, 2018 11:09
add PATCH to custom_objects_api
documentation update: never let cluster-scoped resources skip webhooks
Comment thread CHANGELOG.md
# v6.0.0b1
- Update to Kubernetes 1.10 cluster
- New API: add PATCH to CustomObjectsApi [kubernetes-client/gen#53](https://github.com/kubernetes-client/gen/pull/53)
- Documentation update: never let cluster-scoped resources skip webhooks [kubernetes/kubernetes#58185](https://github.com/kubernetes/kubernetes/pull/58185)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Just curious, are you manually generating this? I would be beneficial to all clients if we can automate this. I would create a tracking issue in gen repo for it.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Yes, I manually checked the diff and tracked down the original PRs. It would help a lot if gen could detect the openapi spec change since last time we generated the client

@mbohlool
mbohlool merged commit 1267667 into kubernetes-client:master Mar 9, 2018
@roycaihw
roycaihw deleted the apichange-6.0 branch March 9, 2018 19:50
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.

2 participants