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.

Sign up for GitHub

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

Jump to bottom

handle status #4

Closed
clux opened this issue Nov 27, 2021 · 0 comments · Fixed by #34
Closed

handle status #4

clux opened this issue Nov 27, 2021 · 0 comments · Fixed by #34
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@clux
Copy link
Member

clux commented Nov 27, 2021

Status needs a #[kube(status = ...)] instruction.

Should be present in crds whose yaml contains:

    subresources:
      status: {}

which should be detectable through the CustomResourceDefinition's picked Version
@clux clux added good first issue Good for newcomers help wanted Extra attention is needed labels Nov 27, 2021
flaper87 added a commit to flaper87/kopium that referenced this issue Feb 16, 2022
@flaper87
Set status explicitly in the kube tag
ef69c43 
Without this, the status data won't be accessible through the generated struct

fixes kube-rs#4

Signed-off-by: Flavio Percoco <flaper87@gmail.com>
@flaper87 flaper87 mentioned this issue Feb 16, 2022
Merged
flaper87 added a commit to flaper87/kopium that referenced this issue Feb 16, 2022
@flaper87
Set status explicitly in the kube tag
518bea0 
Without this, the status data won't be accessible through the generated struct

fixes kube-rs#4

Signed-off-by: Flavio Percoco <flaper87@gmail.com>
flaper87 added a commit to flaper87/kopium that referenced this issue Feb 16, 2022
@flaper87
Set status explicitly in the kube tag
f46fe5d 
Without this, the status data won't be accessible through the generated struct

fixes kube-rs#4

Signed-off-by: Flavio Percoco <flaper87@gmail.com>
flaper87 added a commit to flaper87/kopium that referenced this issue Feb 16, 2022
@flaper87
Set status explicitly in the kube tag
3ad7857 
Without this, the status data won't be accessible through the generated struct

fixes kube-rs#4

Signed-off-by: Flavio Percoco <flaper87@gmail.com>
@clux clux closed this as completed in #34 Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Set status explicitly in the kube tag flaper87/kopium
1 participant
@clux