Skip to content

Conversation

phillip-kruger
Copy link
Member

@phillip-kruger phillip-kruger commented May 8, 2025

This PR introduce a new module in Quarkus called assistant, that allows extensions to talk to an assistant (if any is added)

For now this can work with Chappie (we need to wait for this to be released and then release a new Chappie version)

Once this PR is in, extensions can start making use of the assistant feature, example OpenAPI (#47872) :

chappie_openapi

TODO:

  • Confirm the naming. Should this be named Assistant ?
  • Confirm the "branding". Currently using "warn" colors. Maybe it should be something else ? Quarkus Blue ? Pink ?
  • Confirm if Chappie extension in Quarkiverse should be merged with this ? (There is only a deployment)

@quarkus-bot quarkus-bot bot added area/dependencies Pull requests that update a dependency file area/openapi area/smallrye area/vertx labels May 8, 2025
Copy link

github-actions bot commented May 8, 2025

🎊 PR Preview 2c91ef1 has been successfully built and deployed to https://quarkus-pr-main-47756-preview.surge.sh/version/main/guides/

  • Images of blog posts older than 3 months are not available.
  • Newsletters older than 3 months are not available.

@phillip-kruger phillip-kruger marked this pull request as ready for review May 8, 2025 06:36

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

@phillip-kruger phillip-kruger force-pushed the chappie-extension-enablement branch 3 times, most recently from d7a89cd to 09181ee Compare May 9, 2025 06:12

This comment has been minimized.

This comment has been minimized.

@phillip-kruger phillip-kruger force-pushed the chappie-extension-enablement branch from 09181ee to 77389fe Compare May 9, 2025 06:54
@quarkus-bot quarkus-bot bot added area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins area/documentation labels May 9, 2025

This comment has been minimized.

This comment has been minimized.

@phillip-kruger phillip-kruger force-pushed the chappie-extension-enablement branch from 77389fe to d79b1cf Compare May 12, 2025 00:06

This comment has been minimized.

@phillip-kruger phillip-kruger force-pushed the chappie-extension-enablement branch from d79b1cf to 86c65b0 Compare May 12, 2025 00:43
@phillip-kruger
Copy link
Member Author

@maxandersen @cescoffier - as discussed, I moved the Build Items that extensions will depend on to a spi. I was also wondering if we should not move chappie (from quarkiverse) into the assistant extension.

Initially we wanted to keep it outside of core repo because

  • we did not want to create a new extension in core repo, but now we have anyway with assistant.
  • wanted chappie to evolve at a faster cadence than core repo, but the reality is that the reverse it true.
  • have the ability to add features quickly and not have to wait for a core release, but the reality is the extension point is the extensions, so new features will be added by adding code to the extension.

What do you think ?

This comment has been minimized.

This comment has been minimized.

@phillip-kruger phillip-kruger force-pushed the chappie-extension-enablement branch 2 times, most recently from 5bbfe5e to 5704d1a Compare May 29, 2025 09:02
@phillip-kruger phillip-kruger marked this pull request as ready for review May 29, 2025 09:07

This comment has been minimized.

@phillip-kruger
Copy link
Member Author

@maxandersen @cescoffier - ready for review. Let's get this in and roll forward

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

@phillip-kruger phillip-kruger force-pushed the chappie-extension-enablement branch from 82d5344 to e0d2528 Compare May 30, 2025 02:18

This comment has been minimized.

@phillip-kruger phillip-kruger requested a review from cescoffier May 30, 2025 06:43
@phillip-kruger phillip-kruger force-pushed the chappie-extension-enablement branch from e0d2528 to 6d71988 Compare May 30, 2025 10:13

This comment has been minimized.

This comment has been minimized.

@phillip-kruger phillip-kruger force-pushed the chappie-extension-enablement branch from 6d71988 to de28818 Compare June 2, 2025 01:00
Signed-off-by: Phillip Kruger <[email protected]>
@phillip-kruger phillip-kruger force-pushed the chappie-extension-enablement branch from de28818 to c22663a Compare June 2, 2025 01:00
Copy link

quarkus-bot bot commented Jun 2, 2025

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit c22663a.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

This comment has been minimized.

Copy link

quarkus-bot bot commented Jun 3, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit c22663a.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

@phillip-kruger phillip-kruger merged commit f492474 into quarkusio:main Jun 3, 2025
111 of 113 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.24 - main milestone Jun 3, 2025
@agoncal
Copy link
Contributor

agoncal commented Jul 17, 2025

I wanted to add this extension to my project, but could not find it:

$ quarkus extension list --installable | grep assistant

$ quarkus extension list --installable --category "ai"

I still can install it:

$ quarkus extension add assistant

[SUCCESS] ✅  Extension io.quarkus:quarkus-assistant has been installed

Not sure that it belongs to a category. Shouldn't it be available in the "ai" category?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants