Generated description of nested arguments can be erraneous

[estellesoulard]

In the iam_policy resource, we have two occurrences of the argument organization_id: one on the top level and the other in the rule nested blocks. They have different descriptions :

• the top level organization_id is optional, it can default to the provider organization_id
• the organization_id nested in each rule does not default, either it or project_ids must be set.

The issue is: in the generated Crossplane files, both organization_id arguments end up with the top level description. This is misleading, since the documentation mentions the rule organization_id can default (while it cannot).

Our source appears correct, the issue seems to come from within the generation process.
Upjet appears to not be handling argument nesting properly.

I have filed an upjet issue: crossplane/upjet#548

Once it is fixed upstream, regenerate iam_policy files.