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

FEAT: Produce from Message #247

Open
2 tasks done
jaredbarranco opened this issue Mar 25, 2024 · 2 comments
Open
2 tasks done

FEAT: Produce from Message #247

jaredbarranco opened this issue Mar 25, 2024 · 2 comments
Labels
scope/backend Related to backend changes scope/frontend Related to frontend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature
Milestone

Comments

@jaredbarranco
Copy link

Issue submitter TODO list

  • I've searched for an already existing issues here
  • I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?

As far as I can tell, in order to "re-produce" a message into a topic, you have to copy/paste the payload, key, and headers, then dropdown the partition and serde settings.

Describe the feature you're interested in

An addition to the hamburger menu on each message row that is something like: Produce which then opens the Produce Message pane with the information autofilled from the message. This likely should be added to RBAC as a permission, as not everyone knows the consequences of re-publishing an event/message into a given topic.

v1 should likely only allow exact replicas of data to be produced. Future versions to allow modification of payload, headers, etc.

Feature Extensions:

  • Producer Templates allow for re-use and modification

Workflow screenshots below:

  1. Consume messages from topic (filters optional)
    image

  2. Select from hamburger menu: Produce Message
    image

  3. Produce Message sidebar opens with information autofilled from message
    image

Describe alternatives you've considered

Some alternatives I've considered:

  • Use a small script/cli to GET the message I want to produce, then curl POST to the /messages with the info auto filled

Version you're running

2956664

Additional context

No response

@jaredbarranco jaredbarranco added status/triage Issues pending maintainers triage type/feature A brand new feature labels Mar 25, 2024
@kapybro kapybro bot added status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Mar 25, 2024
Copy link

Hello there jaredbarranco! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

@Haarolean Haarolean added type/enhancement En enhancement/improvement to an already existing feature scope/frontend Related to frontend changes scope/backend Related to backend changes and removed type/feature A brand new feature status/triage/manual Manual triage in progress labels Mar 26, 2024
@Haarolean Haarolean moved this from Unscheduled to 2.0 in Roadmap Mar 29, 2024
@github-project-automation github-project-automation bot moved this to Unscheduled in Roadmap Mar 29, 2024
@Haarolean Haarolean moved this from 1.1 to Next in Roadmap Oct 4, 2024
@github-project-automation github-project-automation bot moved this to Pending Requirements in UI/UX Design Solutions Oct 18, 2024
@Haarolean Haarolean moved this from Pending Requirements to Design Todo in UI/UX Design Solutions Oct 18, 2024
@fahrradflucht
Copy link

fahrradflucht commented Dec 27, 2024

Because it's not quite clear from this request, I think it would be super cool if it would be possible to do this across topics. Use case would be to look at a message from a dead letter topic in Kafbat and retry it. 🙂

@Haarolean Haarolean moved this from Next to 1.2 in Roadmap Dec 31, 2024
@Haarolean Haarolean added this to the 1.2 milestone Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope/backend Related to backend changes scope/frontend Related to frontend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature
Projects
Status: Todo
Status: 1.2
Status: Pending Requirements
Development

No branches or pull requests

3 participants