Publish non-sensitive outputs in atProvider

[bobh66]

What problem are you facing?

We have some functionality that we need to implement in Terraform because the crossplane aws provider does not yet support the required resources. The Terraform is creating objects that are dependencies for other resources in the composition, so we need a way to enforce the dependency chain to prevent the other resources from failing to create because the Terraform hasn't completed yet.

How could Crossplane help solve your problem?

If the Terraform provider could publish it's non-sensitive outputs in the atProvider section, they could be used to create dependencies with other resources in the composition, so that those resources would not attempt to execute until the Terraform had completed.

Sensitive outputs can still be published in the connection secret, although there may be use cases where it would be useful to have access to sensitive outputs in the composition.

[bobh66]

I have started a PR for this, but I am not a golang developer, so I'm sure it needs work. I will push the PR for review and rework,