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

Don't use kube.proto in kube.go. #81

Merged
merged 3 commits into from
Oct 23, 2023
Merged

Don't use kube.proto in kube.go. #81

merged 3 commits into from
Oct 23, 2023

Conversation

mwhittaker
Copy link
Member

Previously, ReplicaSetConfig in kube.proto was used in two ways. It was serialized and passed to the babysitter, and it was used internally by kube.go. This PR refactors kube.go to use a deployment struct instead of a ReplicaSetConfig. This will enable me to simplify ReplicaSetConfig in a future PR.

@mwhittaker mwhittaker self-assigned this Oct 19, 2023
Base automatically changed from strike_writers to main October 19, 2023 23:56
Copy link
Collaborator

@rgrandl rgrandl left a comment

Choose a reason for hiding this comment

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

Nice change.

internal/impl/kube.go Outdated Show resolved Hide resolved
Previously, `ReplicaSetConfig` in `kube.proto` was used in two ways. It
was serialized and passed to the babysitter, and it was used internally
by `kube.go`. This PR refactors `kube.go` to use a `deployment` struct
instead of a `ReplicaSetConfig`. This will enable me to simplify
`ReplicaSetConfig` in a future PR.
@mwhittaker mwhittaker force-pushed the no_proto branch 2 times, most recently from 5f0d158 to ac7cdb7 Compare October 23, 2023 19:39
@mwhittaker mwhittaker merged commit 0ee9ba0 into main Oct 23, 2023
8 checks passed
@mwhittaker mwhittaker deleted the no_proto branch October 23, 2023 19:49
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