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

Refactor TrustZone to extract a repeated Cluster message #25

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

markgoddard
Copy link
Contributor

@markgoddard markgoddard commented Jan 17, 2025

This change refactors the TrustZone message to extract per-Kubernetes cluster details into a Cluster message. They are currently embedded into the TrustZone message as a repeated field, but will eventually be referenced by name or ID.

The Cluster.kubernetes_cluster field has been renamed to Cluster.name.

Field numbers in the TrustZone message have been defragmented.

Required for cofide/cofidectl#126

Backward incompatible change, but worthwhile after the cluster refactor.
@markgoddard markgoddard self-assigned this Jan 17, 2025
Copy link

github-actions bot commented Jan 17, 2025

The latest Buf updates on your PR. Results from workflow buf-ci / buf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed⏩ skippedJan 17, 2025, 4:51 PM

markgoddard added a commit to cofide/cofidectl that referenced this pull request Jan 17, 2025
This change modifies cofidectl to adapt to the changes in
cofide/cofide-api-sdk#25, in which the TrustZone
message has been refactored to extract per-Kubernetes cluster details
into a Cluster message.

For now we restrict the number of clusters per trust zone to one.
Clusters are not yet exposed by the CLI as separate from trust zones.
They are currently embedded into trust zones in the data model but will
be referenced by name or ID in future.

Fixes: #126
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants