Cristian Le

How is this different then applying the profile yaml as a `main.fmf`? Maybe it has overlap with setting system/user/project metadata file/tree

Well this is to help with using `fmf` outside `tmt` context, e.g. #207. I think this would be helpful to convert the dictionary data from the yaml fmf file to...

I can take a quick look into `attrs` before thinking of how to get the minimum framework there. But are there any other libraries to check other than that? Currently...

Indeed, so far the only thing that works is displaying a badge on the top page. The commit status are still displayed as red cross, which is the main complaint...

> FWIW another workaround I had in mind was setting a special `output:` in the previous jobs and suppressing the statuses on the step level That is the ugly approach...

> My point was that you'd have to use `continue-on-failure` on the step level, analyze that step's result and write a new output. :open_mouth: I did not see that you...

That is not ideal because I want to make my playbooks and roles portable to share it with colleagues and only have the keepass integration on the inventory.

This would still not be able to be used within the inventory and would not make it as portable

Here's an example setup: Me an my colleague have different clusters with different inventory setups like: ```yaml # Personal inventory that uses keepass # /host_vars/my_host_A.yaml secret_CA_root_key: "{{ lookup('viczem.keepass.keepass', 'Root CA',...

I don't think the `/path/to/save` is much useful for the `lookup`. The user could use the module `attachment` for that. In the backend, if we don't want to add more...