Update generated IAM acceptance tests to include conditions, or omit IAM conditions from missing test detector

[SarahFrench]

What kind of contribution is this issue about?

MMv1-based resource

Details

When new resources are added to the provider and associated IAM resources are added at the same time there are missing test detector messages like this: GoogleCloudPlatform/magic-modules#10757 (comment)

The PR author doesn't have power to update the IAM resource tests because they are generated, and the PR reviewer needs to know context about IAM resource generation.

I imagine that generated IAM resource tests don't include conditions because they aren't available for all IAM resources, which is fair enough! If that is the case it would be good to come up with a way to either stop the missing test detector flagging condition arguments in IAM resources, or enable conditions to be conditionally included in generated IAM acc tests.

References

No response

[SarahFrench]

See also this list: GoogleCloudPlatform/magic-modules#10757 (comment)

[melinath]

We should be able to detect whether a resource supports IAM conditions at generation time using the presence / absence of iam_conditions_request_type. For example, see:

• https://github.com/GoogleCloudPlatform/magic-modules/blob/90d184014297ccf2c1d06fd6fc01c539832ce638/mmv1/templates/terraform/examples/base_configs/iam_test_file.go.erb#L205
• https://github.com/GoogleCloudPlatform/magic-modules/blob/90d184014297ccf2c1d06fd6fc01c539832ce638/mmv1/templates/terraform/resource_iam.html.markdown.erb#L74
• https://github.com/GoogleCloudPlatform/magic-modules/blob/90d184014297ccf2c1d06fd6fc01c539832ce638/mmv1/templates/terraform/iam_policy.go.erb#L197

[melinath]

Weirdly we still add the conditions field to the IAM resources regardless - we just don't document them.