In Crossplane, we have a tagging convention for all managed resources but they are not implemented in Jet AWS.
How could Crossplane help solve your problem?
We can possibly add a simple templating to provider-jet-aws to produce getters/setters for spec.forProvider.tags field, if it exists, and use that in a custom initializer that can be wired up in Setup function. Though the last one probably requires a Terrajet change.
What problem are you facing?
In Crossplane, we have a tagging convention for all managed resources but they are not implemented in Jet AWS.
How could Crossplane help solve your problem?
We can possibly add a simple templating to provider-jet-aws to produce getters/setters for
spec.forProvider.tagsfield, if it exists, and use that in a custom initializer that can be wired up inSetupfunction. Though the last one probably requires a Terrajet change.