Eron Wright
Eron Wright
Thanks @awoimbee and @Makeshift , I believe this is a variant of a well-known issue, that when the system 'adopts' an existing object, it might also be planning to delete...
@dependabot resume
@dependabot /rebase
I take this as a feature request to provide for global customization of the Workspace. I suppose the operator could have a cluster-scoped and/or namespace-scoped configuration object, providing a default...
See also: https://github.com/pulumi/pulumi-kubernetes-operator/issues/797
This thread seems to say that Pulumi is trying to provision a new server and thus hitting a resource quota. It asserts that using `PATCH` versus `PUT` would solve it....
A perhaps obvious solution would be to produce a separate library for each Azure API, all tied to the "azure-native" plugin. This would force the user to have more fine-grained...
Thanks for the report, will consider a change for next release.