Skip to content
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.

fix(spec): add optional tag in struct fields #311

Merged
merged 1 commit into from
Oct 5, 2017

Conversation

surajssd
Copy link
Member

@surajssd surajssd commented Oct 4, 2017

portMappings was added as an option to ports in services which is
option to ports, initially ports was a compulsory field but with
portMappings addition, either field can be specified. So adding
+optional tag to both fields.

`portMappings` was added as an option to ports in services which is
option to `ports`, initially `ports` was a compulsory field but with
`portMappings` addition, either field can be specified. So adding
`+optional` tag to both fields.
@surajssd surajssd requested a review from concaf October 4, 2017 16:23
@kadel
Copy link
Member

kadel commented Oct 5, 2017

Is there a way to define that one or the other has to be set?

@surajssd
Copy link
Member Author

surajssd commented Oct 5, 2017

@kadel could not find any!

Even in probes (livenessProbe or readinessProbe) one form of handler is needed, but in code in upstream all of them are +optional

https://github.com/surajssd/kedge/blob/96e5dd0db930ceada1f1c51e695f95b97e05eeee/vendor/k8s.io/client-go/pkg/api/v1/types.go#L1859

@kadel
Copy link
Member

kadel commented Oct 5, 2017

OK, thank you.
If this become problem we will have to handle that somewhere else. But this is ok for now.

@kadel kadel merged commit 3fccda7 into kedgeproject:master Oct 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants