Update `ackgenconfig` to be field-focused

brycahta commented 2 years ago

Summary

Some ackgenconfig - such as renames - use an operation-centric approach meaning an operation is required to define a rename config and consume it in code. This current experience is not optimal because it increases cognitive load for both users of the interface and maintainers of the implementation since they need to "know" about this operation detail and pass it around the codebase to use it. This results in higher barriers to entry for users, contributors, and maintainers. Migrating to a field-focused approach is more intuitive and will not require knowledge of operations to use.

Context

This is the parent issue to track and implement changes to move configs from an operation-centric model to a field-focused approach. The proposal detailing the approach can be found here.

Prerequisites

[ ] https://github.com/aws-controllers-k8s/community/issues/1184

Implementation

[ ] Design and approve updated interface for RenameConfig
[ ] Add field-focused RenameConfig to FieldConfig with helpers/accessors
[ ] Update implementation to use field-focused RenameConfig in favor of op-centric renames, if present
[ ] [Local/Soak Testing] Update controllers' generator.yaml and replace op-centric renames with field-focused RenameConfig (do NOT edit the generator.yaml in controller's repo yet)
[ ] Release updated runtime/code-generator with field-focused RenameConfig
[ ] Update controllers' generator.yaml in their respective repos to use updated RenameConfig
[ ] Deprecate op-centric renames from code-generator
[ ] Identify remaining op-centric configs and repeat
- Completing this migration for a single config first so it can serve as a sample/guide. Then, others can work on other configs in parallel

ack-bot commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

ack-bot commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle rotten

a-hilaly commented 2 years ago

/lifecycle frozen

aws-controllers-k8s / community