Jay Pipes

@russmackenzie we're going to keep these service controller issues open since they are on the Service Controller Roadmap project and provide a good top-level landing page...

I think we are likely to want different drift remediation seconds values per resource. I think a CLI option structured like so would probably work: ``` --drift-remediation-seconds-default= ``` would apply...

Apologies @sergey-telpuk, but SQS has lagged behind :( I hope to get back to working on it this quarter.

Unfortunately, the code generator needs to be refreshed to work with attribute-based field definitions like SNS and SQS. This refresh work is not easy and I need to find time...

@dlgordon you rock. thank you for taking the initiative here and making some progresson the SQS controller. I'd be more than happy to review a PR from you and collaborate...

> Based on the latest updates here, should [the Project Stage on the SQS controller](https://aws-controllers-k8s.github.io/community/docs/community/services/) be updated to `PLANNED`? Yeah... it actually should be in `IN PROGRESS` project stage. That...

@dfarr The problem with controller-generated names is that they essentially make the resource impossible to manage using a fully declarative, GitOps-style configuration management system... Because the Spec for the resource...

Hi @Benedikt1992! The way we handle this in ACK's code-generator is to append the suffix `_SDK` to shapes that overlap with publicly-defined names in CRDs. When I get back home...

@dlgordon thanks for putting this issue together. I will work on this starting next week (just heading back from KubeCon today...)

The reason for this is because there is an assumption that the List/ReadMany API call will have had some filtering field set on the input shape to limit the results...