v0.10 changes string outputs to boolean which can cause patching to fail silently

[bobh66]

What happened?

v0.10 added support for nested object outputs, which also has the effect of NOT stringifying the existing outputs, so if an output is a bool that used to get converted to a string, now it stays a bool . This can cause silent failures in patching if the target of the patch is something like metadata.annotations.foo that won't accept a bool.

How can we reproduce it?

Define a Workspace with a boolean output, and observe that prior to v0.10 it is a string in status.atProvider.outputs but after v0.10 it is now a bool.

What environment did it happen in?

• Provider Version: 0.10