Support for Crossplane.io Resources

[kgochenour]

What problem are you facing?

I was experimenting with adding this function to my AWS Resources, and noticed the pipeline was running but not tagging anything.

I noticed in the filter that it only supports resources in *.aws.upbound.io/*, however my resources use *.aws.crossplane.io/* from the provider-aws repo.

How could this Function help solve your problem?

Add support for the Crossplane AWS Provider in addition to the Upbound provider.

[stevendborrelli]

Hello @kgochenour is this something you would be interested in submitting a Pull Request for? One of the issues is that provider the tag types are not consistent between managed resources. I won't have the bandwidth to implement this change.

For example:

One tag type like in s3 is an array of { key:, value: } objects https://github.com/crossplane-contrib/provider-aws/blob/dac903cc6e7f397116fd1f3ee9ea6a725d489488/apis/s3/v1beta1/tagging_types.go#L23

tags:
  - key: key1
    value: val

The other tag type seen in resources like eks is a map[string]string https://github.com/crossplane-contrib/provider-aws/blob/dac903cc6e7f397116fd1f3ee9ea6a725d489488/apis/eks/v1beta1/types.go#L146 which is equivalent to the upjet provider types:

tags:
   key: value
   key2: value2