Add Update/Delete API functionlity for kafkaconnect worker configurations

[eliax1996]

Describe the bug

I am constructing a CI/CD pipeline that spawns custom connectors (JVM workers) on MSK, they require to be launched with a custom worker configuration.
I tried to search on the source code of aws-cli and the doc but seems that isn't possible to delete a worker configuration but only create a new one.
How can I delete/update a custom configuration when I have to update the worker's config?

There is any solution to this problem? If not, there is the possibility to contact the kafka connect team to understand if is possible to implement this feature?

Expected Behavior

being able to delete and update a worker configuration (at least when there are no connectors that are using a certain configuration)

Current Behavior

It is possible only to create a new worker configuration

Reproduction Steps

going to the documentation page available here and view that there is only create-worker-configuration command and not the delete or update one

Possible Solution

Implement an update/delete api

Additional Information/Context

No response

CLI version used

aws-cli/2.5.5 Python/3.9.12 Darwin/21.6.0 source/arm64 prompt/off

Environment details (OS name and version, etc.)

MacOS Monterey 12.5

[tim-finnigan]

Hi @eliax1996 thanks for reaching out. I can try reaching out to that service team and see if adding that API functionality is something they would consider. I'll also transfer this issue to our cross-SDK repository and will post an update here when I hear back.

[tim-finnigan]

P69222695

[tim-finnigan]

I just heard back from a member of the MSK team. They said that the updating/deletion of worker configurations from MSK Connect is not currently supported but that capability is on the roadmap. I can't give a definite timeline but feel free to check back here in the future. If you need to delete resources to avoid service limits (which default to 100 resources per region per this documentation), please raise contact AWS Support to request a limit increase in the meantime.

[github-actions]

This issue is now closed.

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[ssakuh]

Hi @tim-finnigan,
Could you please reach out again to MSK team about this?

[tim-finnigan]

Hi @ssakuh - I reached out for an update and can confirm that the MSK team is still tracking this request. We can't share specific timelines but I would expect some traction on this in the coming months.

[miguelzenteno]

why is it closed if it hasn't been fixed or released yet? is there an open issue to follow this?

[tim-finnigan]

This feature request is still being tracked internally and on the service team's roadmap. It was escalated to the MSK Connect team and closed here because the SDK teams do not directly implement service API requests. You can reach out through AWS Support for more information, review blog posts for new announcements, or refer to SDK changelogs for updates related to this.

[michal-kosinski]

https://aws.amazon.com/about-aws/whats-new/2024/03/amazon-msk-connect-deleting-worker-configurations-tagging-resources/