-
Notifications
You must be signed in to change notification settings - Fork 5
feat: tenant tagging pipeline draft #414
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
base: dev
Are you sure you want to change the base?
Conversation
| for x in list(temporal_extent.values()) | ||
| ] | ||
| ] | ||
| "interval": [normalized_values] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@smohiudd do you know if this is where the existing date bug is?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it may be in the ingest API
| type=["null", "string"], | ||
| description="STAC catalog endpoint URL to fetch all collections from (optional if collections is provided)" | ||
| ), | ||
| "tenant": Param(default=None, type="string", description="Tenant ID to tag the collection with (will be set as eic-tenant property)"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because tenant filter field is configurable in the backend should we use two keys in this config tenant_filter_field and tenant_filter_value?
https://github.com/NASA-IMPACT/veda-backend/blob/dbd05924d7c04eeeec9ed88cc445a7b33a312261/stac_api/runtime/src/config.py#L103
Summary:
https://github.com/NASA-IMPACT/veda-architecture/issues/677
Changes
PR Checklist
terraform validateandterraform plan