Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

Sign up for GitHub

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

Jump to bottom

HTTP API #29

Closed
Sei4or opened this issue Dec 15, 2020 · 0 comments · May be fixed by #39
Closed

HTTP API #29

Sei4or opened this issue Dec 15, 2020 · 0 comments · May be fixed by #39
Labels
enhancement New feature or request

Comments

@Sei4or
Copy link
Contributor

Sei4or commented Dec 15, 2020 •
edited
Loading

In order to give more runtime control, an HTTP API would allow outside sources (whether they be automated or manual) to manage Influo. This includes manual procedures (maybe approved with a POST request), retrieving the current status of procedures (like current command and stdout), and possibly scheduling deploys.

Projects must also now include a name for identification.

Planned Endpoints

  • GET /projects - Returns array of projects
  • GET /projects/:project_name/procedures/ - Returns array of procedures
@Sei4or Sei4or added the enhancement New feature or request label Dec 15, 2020
@Sei4or Sei4or mentioned this issue May 2, 2021
Draft
6 tasks
@Danktronics Danktronics locked and limited conversation to collaborators Sep 3, 2021
@Sei4or Sei4or closed this as completed Sep 3, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

0.4.0 - Pipelines & HTTP API Danktronics/Influo
1 participant
@Sei4or