Who is this for and what problem do they have today?
Currently, running rpk --version prints the Redpanda release version but does not provide the Redpanda Connect release version. This creates confusion for users who need to determine the specific version of Redpanda Connect.
What are the success criteria?
Users should be able to query rpk for the currently installed version of Redpanda Connect.
We could support rpk connect --version to report the Redpanda Connect version information.
Why is solving this problem impactful?
Redpanda Connect and rpk are on different release schedules so it's possible that a new version of Redpanda Connect is released and rpk connect is using an older version. For users to understand what features are available, they must be able to query rpk for the version of Redpanda Connect.
Who is this for and what problem do they have today?
Currently, running
rpk --version
prints the Redpanda release version but does not provide the Redpanda Connect release version. This creates confusion for users who need to determine the specific version of Redpanda Connect.What are the success criteria?
Users should be able to query
rpk
for the currently installed version of Redpanda Connect.We could support
rpk connect --version
to report the Redpanda Connect version information.Why is solving this problem impactful?
Redpanda Connect and
rpk
are on different release schedules so it's possible that a new version of Redpanda Connect is released andrpk connect
is using an older version. For users to understand what features are available, they must be able to queryrpk
for the version of Redpanda Connect.Additional notes
JIRA Link: CORE-4209