API First #462
Labels
No Label
backups
blog
bootstrapping
bug
changes-requested
cli
documentation
duplicate
enhancement
facts
help wanted
invalid
Inventory
low_prio
manager
modules
needs-review
networking
packaging
question
secrets
template
test
tooling
user-testing
vm
wontfix
No Milestone
No project
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: clan/clan-core#462
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Inconsistency between CLI and API?
I still think every feature should work in the API first, because it is more capable of sending structured data and requests. And also allows easily connecting various frontend, backends, services and other extensions.
https://www.postman.com/api-first/
The current CLI first approach doesn't scale, API bricks all the time and doesn't work. I already opened 4 issue today for various internal server error / inconsistencies with the API. ( just saying its a waste of our time)
We haven't really added any new cli features lately, so not really sure what we should do this with this issue. Buggy code is buggy.
In fact for the API to work we have added flake flags to the cli that we have to now remove again #491