Add ingest.sh script. #164
Merged
Conversation
This file contains 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
|
I've explored this topic further, and it seems that the most effective way to implement an API is by using the In the meantime, the ingest.sh script and command will simplify the ingestion process. |
j08lue
reviewed
Nov 5, 2024
pantierra
force-pushed
the
feature/basic-ingestion
branch
from
a64a9d6 to
bfb84a4
Compare
1 task
ciaransweet
requested changes
Nov 6, 2024
pantierra
force-pushed
the
feature/basic-ingestion
branch
from
bfb84a4 to
fc47b05
Compare
Co-authored-by: Jonas <[email protected]>
pantierra
force-pushed
the
feature/basic-ingestion
branch
from
fc47b05 to
217fdd4
Compare
|
Many thanks for your reviews! ❤️ |
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.
Data Management (data ingestion in a first step) is a common requirement for several of our
eoapi-k8sdeployments and projects.From my perspective we should think about data on eoAPI as "content" and not so much as "configuration". While configuration should be in code and part of the reproducible deployment, content should me managable by an admin user. At some point we probably want to think about building some auth-supported API to allow management, eventually even connecting it to some user interface.
This PR consists in a first simple step to add very basic ingestion as a bash script
ingest.shand the relatedmake ingestcommand, it:rasterpod in the namespaceseoapianddefaultpypgstacon itcollection.jsonanditems.jsonfrom the current directory (can be overridden with the environment variablesEOAPI_COLLECTIONS_FILEandEOAPI_ITEMS_FILE.pypgstacloads the collection and items into the pySTAC postgresql database.Related to EOEPCA/data-access#107
fyi, @j08lue, @emmanuelmathot, @zacharyDez