Skip to content

Check/replace legacy API-KEY usage with JWT based check #9

@nickdos

Description

@nickdos

Looks like the following code is using legacy apikey in a request header, when calling Collectory:

https://github.com/AtlasOfLivingAustralia/pipelines-airflow/blob/develop/dags/load_dataset_dag.py#L71

Collectory is still accepting legacy apikey, so a fix cannot be tested until this ticket has been fixed in the test env:

blocker: AtlasOfLivingAustralia/collectory#241

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions