Configuration on Control Planes is still required #18
Description
What happened?
In PR #14, I believe the wrong field made optional. Instead of in spec.forProvider.configuration, status.atProvider.configuration was made Optional
How can we reproduce it?
Review the YAML generated. spec.forProvider.configuration is still required.
What environment did it happen in?
Provider Upbound version: v0.8.0