abra recipe fetch
can only fetch a single recipe #530
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#530
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
description
The behaviour of
recipe fetch
command has changed in commit 0be532692d (with coop-cloud/abra#353) without changing the description to fit. The command can only fetch a single recipe, it doesn't retrieve all recipes anymore.Current help message:
steps to reproduce
abra recipe fetch
without specifying a recipeexpected result
Per help message the expected result is to fetch all recipes similar to behaviour of
abra catalogue generate
. However, since thecatalogue
subcommand seems to cover that use-case well enough already, I would expect this subcommand to require specifying a recipe and displaying help message whenever it is not specified.actual result
comments
The
recipe
subcommand should stay simple and deal with single recipes only.The catalogue still seems to evolve and as more changes are made in the code around it, it would be beneficial to keep
catalogue
andrecipe
subcommands untangled. I would suggest to leave dealing with (multiple) repositories within thecatalogue
subcommand's duties and perhaps split off more subsubcommands from there later. This command then would require specifying recipes, and so the description would have to be updated accordingly.My boiling hot take!
Let's get the functionality back, I think it was a bug from me in the arg handling...
A test wasn't written 🙃 one would be good...