Read/write machine-readable recipe metadata #173
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#173
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?
It is hard for
abra
to parse category/image link/features/etc. from the README (regex and such).Also, I was thinking, we won't be able to support translations in a README file - we'll probably want to load this info into the documentation somehow also and it would be nice if it could support translation.
We might want
abra
to re-write this metadata as part of a CI/CD process (e.g. upgrading the rating after tests pass). Perhaps updating theHealthcheck
value if we detect that thecompose.yml
has ahealthcheck
key.Maybe it is time for a more structured format for this info that
abra
can easily read?I'm talking specifically about this bit (source):
Any suggestions?
Maybe a
recipe.yml
in the recipe repositories?Describing recipe metadata in a structured wayto Describing recipe metadata in a more machine-readable formatDescribing recipe metadata in a more machine-readable formatto Read/write machine-readable recipe metadataWe're putting this on the backburner for now to reduce churn. The new catalogue generation will just miss some extra metadata but will still be functional.
Not following this up.