-
Notifications
You must be signed in to change notification settings - Fork 19
Closed
Description
Was trying to think of a way to automatically deal with upstream updates, and you've got a couple of things you need to care about here:
- kopium updates -> smarter schemas, should release updates if output changed
- kube updates -> should regenerate schemas to avoid incompatible version problems for users (this library pins kube and k8s-openapi)
- upstream crd updates -> should regenerate, actual api changes
You could maybe do a nightly cron job that checks for any of these updating, and effectively reconciling out a new version as a result of this:
if ! [[ $(cargo outdated -wd1 -p kube) =~ "up to date" ]]; then
cargo upgrade kube
fi
if ! [[ $(cargo outdated -wd1 -p k8s-openapi) =~ "up to date" ]]; then
cargo upgrade k8s-openapi
fi
# something to check kopium version
# something to detect crd updates from gateway-api
# if anything changed
if something_changed;
cargo release minor --execute
fithose rely on cargo-edit, cargo-outdated and cargo-release (which there may be some github actions for).
Alternatively, you could just rely on dependabot to detect kopium/kube/k8s-openapi version changes, and manually release this.
shaneutt