Rethink the output of ACK's code generator #1299
Labels
area/code-generation
Issues or PRs as related to controllers or docs code generation
area/crossplane
Issues or PRs related to crossplane
kind/enhancement
Categorizes issue or PR as related to existing feature enhancements.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
The
ack-generate
tool currently consumes the API model definitions fromaws-sdk-go
for a particular AWS service and outputs generated code for:services.k8s.aws
APIGroupcmd/main.go
, allpkg/resource/*
packages, Helm charts, static config files, etc)While this has served us well over the last couple years, it has become apparent that a more useful system would be to focus on outputting Go packages for the various resource managers (as we do now) but make them able to be easily imported outside of ACK controllers. In other words, solidify the public interface for resource managers and allow systems like Crossplane or Terraform to simply import the relevant Go packages for the various services and their resource managers.
Some subtasks I think are worth doing for this effort:
github.com/aws-controllers-k8s/pkg
repositoryThe text was updated successfully, but these errors were encountered: