viq

Results 12 issues of viq

Configuration without any prefixes defined, thus using only the default `100.64.0.0/10`. A few machines connected. Added IPv6 prefix (shown in examples `fd7a:115c:a1e0::/48`), restarted headscale. Even after restarting their services, existing...

bug

https://docs.ansible.com/ansible/latest/user_guide/playbooks_strategies.html#running-on-a-single-machine-with-run-once says that `run_once` gets executed only on the first host in batch. This makes getting checksums fail for the whole run if that host skips this role for whatever...

According to https://docs.ansible.com/ansible/latest/user_guide/playbooks_strategies.html#running-on-a-single-machine-with-run-once `run_once` means the task runs only on first node in batch. This fails when this role is included using e.g. ```yaml - role: ansible-role-promtail tags: promtail when:...

## Problem Statement Currently, to my understanding, only issues in projects on Gitlab get imported as tasks. Gitlab also has ToDo category, where for example you can add Merge Requests...

enhancement
help wanted
Stale

https://wtfutil.com/modules/google/gcal/ points to https://developers.google.com/calendar/api/quickstart/go which doesn't work with new go. Running https://developers.google.com/calendar/api/quickstart/python instead gives me two files: `credentials.json` and `token.json`. Trying to use `credentials.json` results in ``` Get "https://www.googleapis.com/calendar/v3/users/me/calendarList?alt=json&minAccessRole=writer&pageToken=&prettyPrint=false&showHidden=false": oauth2:...

🐛 bug

It would be great to assign not only people but also servers to groups, to be able to quickly apply access rules to the whole lot of them.

enhancement

The main part that's unclear to me is what it expects as ``

Could you show how to run using pepper something like `salt-run survey.hash '*' pkg.list_upgrades refresh=True`? Or maybe even `salt-run survey.hash 'G@osfinger:debian-8' pkg.list_upgrades refresh=True match=complex` since that passes some parameters to...

**Describe the bug** `oref0-upload-profile` either has issue, or is not documented sufficiently - for someone not using a medtronic pump it seems impossible to use. **To Reproduce** Steps to reproduce...

``` # cat /etc/runrestic/home.toml name = "home directories" repositories = [ "rclone:test",] [execution] parallel = true retry_count = 10 retry_backoff = "1:00 exponential" [environment] RESTIC_PASSWORD_FILE = "/etc/secrets/restic.password" RCLONE_CONFIG = "/etc/secrets/rclone.conf"...