Skip to content

Securing Delete Collection DAG #425

Description

@aliziel

Description

#417 shipped with basic input checks, but would benefit from stricter input validation and/or limiting access.

Airflow isn't able to confirm whether or not the input table name is a feature collection and is safe to drop. Anyone with instance access can also run the DAG.

Determine whether the DAG will be triggered from Airflow, externally, or both to inform appropriate access + validation checks.

See recent Keycloak/SM2A integration and DAG Launcher work for possible service to service uses.

Acceptance Criteria

  • Additional safety measures set up to prevent destruction of non-collection database objects

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions