fmf
fmf copied to clipboard
Flexible Metadata Format
- [x] implement the feature - [x] write the documentation - [x] extend the test coverage
Replace `.pop()` calls with skipping "control" keys (when,because..) during the merge.
Include a special key `fmf-name` in the `data` dictionary during the `filter` execution so that it's possible to filter based on the fmf node name as well.
WDYT? Todo: - [x] find BETTER_NAME for this helper function - [x] Documentation - [x] smuggle '-~' operator (delete if matches regexp)
Example: ```yaml my_var: - one - two /overwrite: my_var-: [ two, three ] my_var+: [ three, four ] ``` This one gives `my_var: one and four` which would be inconsistent...
Pull Request Checklist * [x] implement the feature * [ ] write the documentation * [ ] extend the test coverage
Even though the original filter description is correct and does not contain any factual flaws it might be confusing to people. There are two improvements that I propose: 1. People...
Looking at https://tmt.readthedocs.io/en/stable/guide.html#inherit-plans ``` discover: how: fmf url: https://github.com/teemtee/tmt prepare: how: ansible playbook: ansible/packages.yml execute: how: tmt /basic: summary: Quick set of basic functionality tests discover+: filter: tier:1 /features: summary:...
Working on packaging `tmt` to homebrew, I've noticed that fmf is missing its sdist
Here are various modernizaitons to the pyproject - Switched to PEP621 - ~~Switched to `src-layout` structure.~~ Dropped as people are opposed to it - Changed the build backend to hatchling...