DRAFT: Amazon q spike
DO NOT MERGE!
What does this MR do and why?
This MR contains the iteration plan for moving the AmazonQ changes which were developed in a private fork to the canonical master branch.
About GitLab Duo with Amazon Q
Over a few months, this feature was developed in a private fork in order to protect the confidentiality until the re:Invent anouncement. The documentation for this feature is already public and in the master branch.
<Insert video demonstrating full feature set><Insert video introducing highlights in the code>
To test these features locally on the GDK, please follow the For Developers instructions on the feature branch's README.
- You might need to make some adjustments to the instructions (for example, checkout a different branch if reviewing an MR)
- For the full AmazonQ integration to work, you'll need a relevant AWS account and a GitLab instance that is accessible to Amazon. For simple testing purposes, it should be sufficient to comment out some interactions.
Iteration Plan
Based on the commits in this branch, here's how we can sequence and parallelize some of the work:
| Parallel Step | Commit | MR |
|---|---|---|
| Step 1 | Feat(Q): Add AmazonQ db and confi | !174949 (merged) |
| Step2 | Feat(Q): Initialize AmazonQ onboarding admin pages | !174952 (merged) |
| Step3 | Feat(Q): Add create/update service for AmazonQ | !175501 (merged) |
| Step3 | Feat(Q): Frontend for AmazonQ admin | !175356 (merged) |
| Step3 | Feat(Q): Add disconnect endpoint | |
| Step3 | Feat(Q): Add AmazonQ quick action | |
| Step3 | Feat(Q): Add Group AmazonQ availability settings | !176100 (merged) |
| Step4 | Feat(Q): Add Project AmazonQ availability settings | !176202 (merged) |
| Step5 | Other polishing stuff (1, 2) | !175064 (merged) |
All of Step5, depends on Step4, which depends on Step3 (etc.), and all the parts under Step5, Step4, and Step2 can be done in parallel.
Edited by Paul Slaughter