wujiuye
The Configuration resource is deleted normally, but if there are other Configuration resources that reference the same Backend, the terraformDestroy logic is skipped and only the resources other than tfstate...
If a newly created configuration references an existing backend (configured by other configurations), then the terraform apply executed by the newly created configuration will actually do nothing because it uses...
I agree with this approach：“By adding a validation”. Reason: From the perspective of the terraform-controller, one configuration resource corresponds to the provisioning of one infrastructure resource. The backend should ideally...
Can kubevela provide a strategy called "shared-component" and implement a reference counter, so that the shared component is only uninstalled after the last referencing application is uninstalled, similar to the...
At the beginning, we also believed that, because the componentName is indeed the name of the configuration resource, many of our designs were based on this assumption. However, kubevela has...
Can you tell me from which version it started to be removed? We are currently using version 1.8.2.
> I just realized specifying `componentNames` in shared-resource policy may solve your problem. Can you check that? @wujiuye I misunderstood your intention here. We have actually tried this approach, and...
没看明白，可以说详细一点吗？
嗯嗯，对的。不过这只是打印验证结果，static{}代码块可以移除的。
嗯嗯，小问题也是问题