ADK2 Future of Agent Config

[cccs-jp]

Hello from @CybercentreCanada !

We ❤️ your work on ADK (and A2A) and are successfully leveraging both for cyber security work.

With the announcement of ADK 2 we've noticed the comment about Agent Config being deprecated in the future and were wondering why that is? Even with it's current limitation, it's very useful to us.

We like it because it's very easy approachable for our analysts, while teams of developers works on complementing the framework with additional tools and more complex code in a side package that we include in all our agents (via yaml and python). With this approach we were able to abstract away authentication, tracing and custom integration with our environment, so our analyst can focus on building cyber security agents. Other config agents framework also provide a similar yaml experience which is great way to get started.

Thanks for your work on this project, hope we can better understand the decision and perhaps make you reconsider to keep it alive within the framework! 🙏

Cheers!

[boyangsvl]

Thanks for the comment. We are not deprecating agent config. We are deprecating those hand-written class in favor of reflection-based agent creation from the config files.

[cccs-jp]

Thanks a lot for this clarification, it make everyone happy here! 😄. Thanks for this amazing framework.