Skip to content
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.

As a user, I want Harvest to be deployable as a service #14

Open
jordanpadams opened this issue Apr 10, 2020 · 1 comment
Open

As a user, I want Harvest to be deployable as a service #14

jordanpadams opened this issue Apr 10, 2020 · 1 comment
Labels
icebox p.wont-have proj.registry+api requirement

Comments

@jordanpadams
Copy link
Contributor

Retrofit Harvest to function in a service-oriented architecture. Part of greater "PDS Discipline Node Client" package.
@jordanpadams jordanpadams added enhancement New feature or request medium Epic labels Apr 10, 2020
jordanpadams added a commit that referenced this issue May 29, 2020
@jordanpadams
Add initial design docs
1681ada 
Primarily copied from the baseline registry design docs, most of this information
is still applicable. Does not yet include requirements.

Refs #19 #14
@jordanpadams
Copy link
Contributor Author

de-prioritizing for the time being as this would be nice if harvest could be triggered remotely, but not required for the foreseeable future.

@jordanpadams jordanpadams changed the title Refactor Harvest to be deployable as a Service As a user, I want Harvest to be deployable as a service Apr 21, 2021
@jordanpadams jordanpadams added requirement and removed Epic enhancement New feature or request labels Apr 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
icebox p.wont-have proj.registry+api requirement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jordanpadams