feat/BACKEND-105 QDRANT Mock Data - #132
Draft
Cryotechnic wants to merge 6 commits into
Draft
Conversation
|
| - name: Configure kubeconfig | ||
| run: | | ||
| mkdir -p $HOME/.kube | ||
| echo "${{ secrets.KUBECONFIG }}" | base64 -d > $HOME/.kube/config |
| component: seed-qdrant | ||
| spec: | ||
| restartPolicy: Never | ||
| containers: |
| command: ["yarn", "seed:qdrant"] | ||
| env: | ||
| - name: QDRANT_URL | ||
| value: "http://planifets-chatbot-qdrant:6333" |
mhd-hi
marked this pull request as draft
June 29, 2026 23:00
Member
|
After talking with other team members, we have decided that this feature is not needed right now since we already fetch live data from ÉTS servers. This PR will not be closed as of now since we may need it in the future. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Closes #105
📖 Description
Ajoute l'infrastructure pour peupler Qdrant avec des données de cours fictives en dev/staging, sans dépendre des données de prod.
Fichiers créés :
seed/qdrant/courses.json: 10 fixtures de cours couvrant 3 programmes (LOG, GTI, ELE) avec payloads conformes àEmbeddingViewDtoseed/qdrant/seed-qdrant.ts: Script de seed idempotent : crée la collection si absente, upsert les points avec vecteurs déterministes (1536 dim, Cosine)k8s/jobs/seed-qdrant-courses.k8s.job.yaml: Job Kubernetes one-shot qui exécute le seed contreplanifets-chatbot-qdrant:6333.github/workflows/dispatch-seed-qdrant.yml: Workflowworkflow_dispatchavec sélecteurdev/staging, applique le Job viakubectl, affiche les logsFichiers modifiés :
package.json: Ajout du scriptseed:qdrantet de la dépendance@qdrant/js-client-restdocker-compose.yml: Ajout du service Qdrant (profildev) pour le développement localDockerfile: Copie du répertoireseed/dans l'image de production.env.example: Ajout des variablesQDRANT_URL,QDRANT_API_KEY,QDRANT_COLLECTIONsrc/jobs/jobs.service.ts: Remplacement du@Cronhardcodé par unCronJobdynamique piloté parJOBS_CRON_SCHEDULE(env var)test/jobs/jobs.service.test.ts: Ajout deSchedulerRegistryau module de test🧪 How Has This Been Tested?
docker compose --profile dev up qdrant -dpuisyarn seed:qdrant→ 10 points upsertés avec succèsGET /collections/coursesconfirmestatus: green,points_count: 10yarn test -- --testPathPatterns="test/jobs/jobs.service.test.ts"→ 3/3 passdocker compose --profile dev up→ app démarre, logRegistering jobs cron: 0 */12 * * *visibleKUBECONFIGconfiguré par environnement pour être testés en cluster☑️ Checklist before requesting a review
🖼️ Screenshots (if useful)
N/A