William Andersson
William Andersson
Updating required fields for a CRD in the Cluster, then applying changes to a CR later does not work
Sorry, @alexsomesan, I thought it was from our open source project, but it was a different one. Here it is: ``` Error: Plugin did not respond with kubernetes_manifest.test-application, on main.tf...
Updating required fields for a CRD in the Cluster, then applying changes to a CR later does not work
Hi @alexsomesan, have you had a chance to look into this?
Updating required fields for a CRD in the Cluster, then applying changes to a CR later does not work
@alexsomesan ? Don't mean to be a nuisance just curious seeing as you asked for the gist :)
Updating required fields for a CRD in the Cluster, then applying changes to a CR later does not work
No worries for the radio silence :) Creating an application is never an issue. I believe you misunderstood my explanation. The case was that we already had an application applied...
Updating required fields for a CRD in the Cluster, then applying changes to a CR later does not work
I understand. It's not a huge surprise that it was our fault and not yours. I agree that some sanity checks should be in place. Would've helped us at least!...
Are there any go to workarounds for this error for the time being? I can't see that it actually ruins anything, but its always a nice comfort having no errors...
@ChaosInTheCRD bump! We would very much like to be able to verify attestations as well
Our application is very large, so I think I would struggle to give a minimal example based on our codebase. Especially considering I'm not familiar with every part of it....
Just for clarification: There is still only one `handleFeatureChange` event that is being triggered when modifying. However, `removeFeature` and `addFeature` is called a lot of times as a result of...
And yes, the modify interaction is rememoed after dropping the feature I'm currently modifying, but it is not being rememoed whilst dragging the feature. I have also checked the map...