Closed mdbooth closed 7 months ago
Name | Link |
---|---|
Latest commit | 564b6bd899062bf4fc06ac4a6a10ddfbe7f7a082 |
Latest deploy log | https://app.netlify.com/sites/kubernetes-sigs-cluster-api-openstack/deploys/65e0965590da6b0008487f05 |
Deploy Preview | https://deploy-preview-1915--kubernetes-sigs-cluster-api-openstack.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
This is so much better design! It looks good to me, but since it already has approved label, I'll leave setting lgtm to the next reviewer.
Nicely done, I suspect the API doc wasn't generated for some reason?
/lgtm
/cc @lentzi90 @mkjpryor @mnaser
@mdbooth: GitHub didn't allow me to request PR reviews from the following users: mkjpryor.
Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: lentzi90, mdbooth
The full list of commands accepted by this bot can be found here.
The pull request process is described here
This change came from attempting to write validation markers for CloudName and IdentityRef in both the machine and cluster specs.
Firstly I noticed that IdentityRef was marked optional in the cluster spec, but it is certainly required: the cluster cannot be provisioned without cloud credentials. I made IdentityRef required in the cluster spec.
In contrast, IdentityRef is genuinely optional in the machine spec because, if not specified, we will use the credentials defined in the cluster spec.
CloudName on the machine spec is also marked optional. However, it is required if IdentityRef was specified. This is because it refers to the same object as IdentityRef. The most sensible way to to represent this in the API is to put it in the IdentityRef. This means that if IdentityRef is provided, it must be provided completely, including CloudName.
/hold