Fix/Update docker compose load-data #177
Open
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.
Un premier fichier load-data avait été créé (par moi) permettant de choisir de lancer la stack docker compose directement ou de la lancer avec chargement des données
Ce chargement de données se fait grâce à l'extension de fichier docker compose (surcharge de plusieurs fichiers à la suite) de cette manière:
docker compose -f docker-compose.yml -f docker-compose-load-data.yml up
Les commandes passées pour le chargement utilisent maintenant les tâches bloom/tasks et attendant à minima 4 fichiers dans le dossier data:
Ce serait pas mal d'ailleurs d'uniformiser les noms dim_port, dim_zone, dim_vessel et ods_spire_ais_data (operationnal data source) ou stg_spire_ais_data (staging) et de mettre à jour un set complet sur le Notion
A documenter, la possibilité de passer ces commandes à la mano du genre: