-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Basic ingest testing #184
Comments
Results
single-asset collectionPattern 1: manually create the collection via the
Pattern 2: manually create the collection via the
Pattern 3: generate a composite dataset config with s3 discovery+pseudo-STAC collection object and submit
Pattern 4: generate a composite dataset config with s3 discovery+pseudo-STAC collection object manually trigger
multi-asset collectionGenerated test metadata for future testing and then confirmed that patterns 1 and 2 fail with the same error as the single-asset collection. I haven't had time to generate the composite dataset config input json for this multi asset test collection yet... |
More test cases! I'm going to link examples here until we setup a home base for workflow test data. |
Purpose
Describe how we can test our most basic VEDA ingest use cases when changes are made to airflow and/or the workflows endpoints for two representative VEDA production collections.
Representative collections
Representative properties for most VEDA collections
Most/all VEDA collections have these properties
Not all VEDA collections have these properties but they eventually should
Missing from this issue (a very incomplete list)
datasets/
endpoint tests (because multi asset configuration is not yet supported, the additional collection properties and multi asset configuration is truncated by the endpoint before the request triggers a pipeline in airflow--there is work in progress to address this)Overview
-temp-test-copy
to the collection id and update the title so it is easy to pick out in the browser).veda-data-store-staging
fromveda-data-store
depending on which mwaa, veda-data-airflow, and veda-backend environment you are testing.STAC_API_URL = ___________
INGEST_API_URL = ___________
WORKFLOWS_API_URL = ___________
AIRFLOW UI URL = ___________
ingest-api/collections
endpoint, then trigger a discovery workflow via theworkflows-api/discovery
endpoint.ingest-api/collections
endpoint, then trigger the veda_discover DAG via the veda-data-airflow UI.workflows-api/dataset
endpoint which manages the collection creation and then triggers a veda_discover DAG. This is not yet able to handle multi asset collections or additional properties yet.veda_dataset_pipeline
via the airflow UI which handles the collection and then discovery as a subdag operation.Examples
Single-asset collection
collection.json
discovery-config.json
dataset-config.json
multi-asset collection
collection.json
discovery-config.json
dataset-config.json
The text was updated successfully, but these errors were encountered: