mconigliaro
mconigliaro
I interrupted `borg create` on its first run and got the `Repository has no manifest` error.
Ah, so this is why when I delete attributes from `.kitchen.yml`, the node keeps using the old values. I didn't realize the point was to try to mimic "normal" attribute...
What a silly bug. Who asked for this forbidden-fields "feature?" How about if we just behave exactly the way kubectl does by **not** forbidding certain fields? 😂
Duplicate of #809?
This is what worked for me: ```yaml provider_raw_config_args: - "customize ['createmedium', 'disk', '--filename', 'example', '--size', '2048']" - "customize ['storageattach', :id, '--storagectl', 'SCSI', '--port', '2', '--type', 'hdd', '--medium', 'example.vdi']" ```
The solutions above won't work with [roles](https://docs.ansible.com/ansible/latest/user_guide/playbooks_reuse_roles.html#role-directory-structure), because playbooks exist at the root level too. That means the only globs that will actually work in all cases are `*.yml` and...
I can do it manually, but won't it be out of date again when you guys cut a new release? I just assumed this inconsistency might be indicative of a...
I got this dumb error on Ruby 2.4, but it worked for me on Ruby 2.3.4.
It looks like something else already configured the root logger (both locally and on AWS), so I made my own, and that seemed to fix it: logger = logging.getLogger('handler') logger.handlers...
This feature would be useful for almost all the CLI commands (not just `verify`).