Skip to content
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

Pipeline dev cycle has too many road humps #44

Open
nerdstrike opened this issue Apr 20, 2022 · 0 comments
Open

Pipeline dev cycle has too many road humps #44

nerdstrike opened this issue Apr 20, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@nerdstrike
Copy link
Contributor

@jenniferliddle wants to be able to flush pipeline task history so that she can iterate on task registration code.

Problems:

  1. Alterations to task_input schema leave a legacy of tasks with bad inputs for latest code that will break new claiming code
  2. Making a new pipeline (unique by name) results in needing to request a new pipeline token from admins
  3. PUT /tasks does let you reset tasks to a certain state, but it is cumbersome for a full reset of all tasks

We need more helpful capabilities (perhaps for development only) to ease development of systems that interact with npg_porch.

@nerdstrike nerdstrike added the enhancement New feature or request label Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant