-
Notifications
You must be signed in to change notification settings - Fork 276
apis: add MeshRootCertificate API types #4677
Conversation
Adds the Go types for the MeshRootCertificate API Part of openservicemesh#4502 Signed-off-by: jaellio <[email protected]>
66643c4
to
093f6a0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The v1alpha1 version of the config API is being updated here, which is no longer used.
type MeshRootCertificateSpec struct { | ||
// Provider specifies the mesh certificate provider | ||
// +optional | ||
Provider *ProviderSpec `json:"provider,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason the only field in the spec is optional? Does an empty spec mean something?
Signed-off-by: jaellio <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #4677 +/- ##
==========================================
- Coverage 69.76% 69.47% -0.30%
==========================================
Files 217 217
Lines 15020 15325 +305
==========================================
+ Hits 10479 10647 +168
- Misses 4491 4628 +137
Partials 50 50
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Signed-off-by: jaellio <[email protected]>
* apis: add MeshRootCertificate API types Adds the Go types for the MeshRootCertificate API Part of openservicemesh#4502 Signed-off-by: jaellio <[email protected]> * Use v1alpha2 Signed-off-by: jaellio <[email protected]> * Update ProviderSpec Signed-off-by: jaellio <[email protected]>
Description:
Adds the Go types for the MeshRootCertificate API
Part of #4502
Affected area:
Please answer the following questions with yes/no.
Does this change contain code from or inspired by another project? no
Is this a breaking change? no
Has documentation corresponding to this change been updated in the osm-docs repo (if applicable)?