Skip to content

Make PatchConnectorCommand more robust againt concurrent config changes #357

@gunnarmorling

Description

@gunnarmorling

See https://github.com/kcctl/kcctl/actions/runs/5699964560/job/15449368506; the scope of the retry loop around one of the API calls seems not to be enough, we should do something similar for the other (read) API call. Perhaps we can extract this retry loop into a re-usable method like so:

Map<String, String> connectorParameters = retrying(() -> kafkaConnectApi.getConnectorConfig(conectorToPatch));

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions