fkusei
fkusei
If there's a port which is currently disabled, but `cdict` is as follows: ```json { "disabled": "false", "hw": "true" } ``` Bundlewrap will generate a `KeyError('hw')` (see blelow), because that...
I just encountered a situaton where it would be nice if an `action` item could state the following: ```python actions['update_cache'] = { 'command': 'do_something', 'triggered_by': { 'file:/some/path/*', }, } ```...
I just did a `bw verify` against one node, which didn't show any pending changes. However, when doing an `bw apply -i`, it prompted me to run an `action`, because...
Probably needs #648 first, so we don't have to add zfs stuff to all items.
I've got some bundles which do some upgrade tasks. To avoid having to define a lot of actions to be triggered in a specific order, i'm using something like this:...
Currently, you have to put a `needs` on `directory:/where/git_deploy/targets` into the `git_deploy` item definition. `git_deploy` should detect that dependency automatically, or even create that directory itself.
In #670, the attribute `content_hash` was added to the list of usable item attributes. Previously, that was only used for checking for differences between locally generated files and those deployed...
It would be nice if `-i` could use an item selector, to tell bundlewrap to only apply this selector interactively. One would use `bw apply -i bundle:something -- node` to...
In our repo we're using a hook which may raise `SkipNode`. However, it's not immediately obvious to the user why the node wasn't applied, especially if there's a lot of...
If you want bundlewrap to not page long stuff even when `STDOUT_WRITER.isatty()` returns true, you have to use something like `PAGER=cat bw metadata ...` It would be nice to be...