Ross Crawford-d'Heureuse
Ross Crawford-d'Heureuse
docs from readthe docs seem to be missing for both role and clusterrole ``` - apiGroups: [apiextensions.k8s.io] resources: [customresourcedefinitions] verbs: [list, watch, patch, get] ```
also the events access was missing from both clusterrole and role
That's a damned good point.. I'll review the scoping as you pointed out.. I think at the point that I got it working I was keysmashing.. so most possible it...
P.S. I was thinking of using something like marshmallow to validate the spec. Is this a strategy you would endorse? or do you have something else in mind? On Sun,...
I was thinking something like either another decorator or appending a `spec_validator` to the current decorator which if present would then validate just pre to being injected into the create|delete|etc|_fn(spec)...
Sorry Nolar, I have combined a question with a ticket. Separate question, how to ensure that the spec provided by the CRD is the expected spec.. is there a prescribed...
+1 can confirm same issue
how does the changing passwords run? not shown here ``` npm run-script Lifecycle scripts included in umami: start next start available via `npm run-script`: dev next dev build npm-run-all build-tracker...
+1 this is fairly recent