Add options for skipping default tags

[mikael-lindstrom]

Description of your changes

The PR introduces the argument --skip-default-tags which makes the provider skip setting the default tags:

• crossplane-kind
• crossplane-name
• crossplane-providerconfig

This is useful for "S3-compatible" services such as Scality Ring which implements all the required API for Crossplane except for tags. Currently the provider fails to create a bucket in Scality Ring since the tag API returns 501 NotImplemented.

Unfortunately this introduces changes to a lot of generated files since hack/main.go.tmpl is modified but the change is small. Unsure if there is a better way to solve this.

Fixes #1141

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable to ensure this PR is ready for review.
• Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

This has been tested against localstack and works as previously without --skip-default-tags, when it's set it correctly skips setting the default crossplane tags for S3 buckets.

We are running this change in production for a week now and it's working fine with the option --skip-default-tags added to the DeploymentRuntimeConfig against Scality Ring which does not support tags.

[github-actions]

This provider repo does not have enough maintainers to address every pull request. Since there has been no activity in the last 90 days it is now marked as stale. 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.

[github-actions]

This pull request is being closed since there has been no activity for 14 days since marking it as stale. If you're still working on this, feel free to reopen the PR or create a new one!

[erikgb]

/reopen

[tenstad]

Would really like this feature, as the "S3-compatible" Cloudian also does not support tags on IAM Policy and User.

[tenstad]

If it's not possible to get this option into the provider config without severe drawbacks, it LGTM!

[erikgb]

@turkenf Any advice on how to get progress on this PR? As a workaround we are currently using the "old" AWS provider for the problematic managed not supporting tags in our S3 "compatible" infrastructure (Cloudian), but this setup seems to "hit the roof" in number of CRDs in our cluster. So we would have no other choice than to fork this provider, which is something we obviously would like to avoid.... 😄