You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.tags
field, if it exists, and use that in a custom initializer that can be wired up inSetup
function. Though the last one probably requires a Terrajet change.The text was updated successfully, but these errors were encountered: