Mauricio Alvarez Leon
Mauricio Alvarez Leon
@pbecotte I just checked the feature gates and you're right. They've moved it into beta with the release of 1.27 back in april! @joey-squid With you being the original author...
latest commit solves the issue from referenced issue, however we still run into this error if the user chooses to set computed_fields and not include `annotations/labels` in the list of...
I've attempted to run the test on my machine but running into issues, could be because im not using kind and instead using minikube: ``` └─(17:43:54 on computed_fields_allUnknown ✹)──> make...
Latest commit addresses the case where API changes the config value set by the user. How it appears in config: ``` ... resources = { limits = { cpu =...
~~I played around more with this and found this config from the original issue to cause a change despite no change actually happening. The original panic doesn't happen however.~~ This...
@theloneexplorerquest you're more then welcome to open a PR! We appreciate contributions from the community to improve the provider. We can assist you on PR if needed
@theloneexplorerquest it makes sense to include both message and reason as part of the log. You can also add those along with lastPhaseTransitionTime. and yes it looks like depending on...
No need for a test since the `stateConf` doesn't have one already made, this is because it's a log output.
Hi @manjinder-mckc ! any help needed for this?
@alexsomesan I'll need some feedback since when I run it through the debug. the plan produces a plannedchange of just the value and not the entire resource. However if we...