Skip to content

decouple harvester app from harvesting #6027

@rshewitt

Description

@rshewitt

User Story

In order to process jobs for catalog when harvester app is down, datagov wants to decouple harvesting from the harvester admin app

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

  • GIVEN the harvester admin app is coupled with harvesting
    WHEN the harvesting app and harvesting admin app are separated
    THEN the harvester app doesn't impact the harvesting process
    [AND optionally another verifiable outcome]

Background

[Any helpful contextual notes or links to artifacts/evidence, if needed]

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions