import cycle not allowed for resolvers/referencers

[haarchri]

What happened?

since we have more and more resources in provider-aws we see go import cycle issues for resolvers/referencers:

• Launch Template and Launch Template Version resources added #1041 (cannot set Resolvers/Referencers for LaunchTemplate & LaunchTemplateVersion in EC2-Instance)
• added s3 resolvers for queueArn, replicaKmsKeyId, kmsMasterKeyId, crossplane:generate:reference #1022 (set Resolvers/Referencers for S3/Lambda)
• feat(iam): Add RolePolicy resource for inline policies #938
• feat(iam-oidc-provider): add reference to eks-cluster #830

How can we reproduce it?

What environment did it happen in?

Crossplane version:

[muvaf]

One way could be to use unstructured.Unstructured in your own custom resolver. Though it'd be nice if we have that in crossplane-runtime similar to the existing strong-typed resolver.

[haarchri]

@muvaf can you provide one example ?

[muvaf]

@haarchri I don't have a concrete example right now. Opened crossplane/crossplane-runtime#313 with a bit more details.

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[josegonzalez]

It would be great to re-open this. Currently there isn't a way to create/update a Launch Template and reference it when creating an ASG, meaning there is extra manual work if your Launch Template ever changes version (which is kinda the whole point of the thing).