Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Construct connection-specific resource names in Internal Kafka REST responses #80

Closed
rohitsanj opened this issue Oct 11, 2024 · 1 comment
Labels
enhancement New feature or request on-hold

Comments

@rohitsanj
Copy link
Contributor

rohitsanj commented Oct 11, 2024

(Mentioned as a followup in #74)

The Internal Kafka REST API responses include "resource_name": null, whereas confluentinc/kafka-rest constructs a "Confluent Resource Name" of the format crn://<authority>/resource=name/sub-resource=name.

We need to construct CRNs based on the type of Confluent-flavored Kafka cluster (CCloud, CP, Confluent Local), as well as determine what the names should default to for non-Confluent flavored clusters.

To start, look for the TODO statement as follows:

// TODO: Construct resource name based on the connection/cluster type
@Cerchie Cerchie self-assigned this Jan 9, 2025
@Cerchie Cerchie mentioned this issue Jan 10, 2025
5 tasks
@Cerchie
Copy link
Contributor

Cerchie commented Jan 10, 2025

stopping work here, no plans to use CRNs in the vscode extension as of this date

@Cerchie Cerchie added enhancement New feature or request and removed on-hold labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request on-hold
Projects
None yet
Development

No branches or pull requests

4 participants