Waldek Maleska

Results 66 comments of Waldek Maleska

I absolutely second everything @mouzfun said, including the preface. I'm thinking that with discrepancy in the comment above by @jefferai and the replies on the google groups, it would be...

Using `vault operator migrate` sounds very elegant. It does sound like it may not be completely safe though (unless you shut Vault down while doing that): https://www.vaultproject.io/docs/commands/operator/migrate > This is...

@michelvocks with all my appreciation for the great application that Vault is and the work, I believe this is not appropriately tagged as `docs` and `enhancement`. Backup/restore is an essential...

For me this is not a dealbreaker at all (apparently!), but it would be a nice thing to have, especially for "access" groups (we currently manage project/group access by sharing...

@klucsik See https://jfrog.com/knowledge-base/how-to-change-artifactorys-service-port/ > Artifactory uses port 8081 by default. In version 6.x this port is also used to access the web UI. > In version 7.x the web UI...

I can confirm that the issue is still very much present and valid on 4.2.0 td-agent / Ubuntu Bionic. We're using it to report on Artifactory stats as part of...

For me - so far, so good. A fairly basic scenario works fine: ``` $ gitlabform --config config_multiple.yml ALL_DEFINED 🏗 GitLabForm version: 3.4.0rc1 = pre-release 🤩 (the latest stable is...

As for the "Any eligible user" rule, I might be using it wrong or something's going on: * Using just `merge_requests_approvals.approvals_required` had no effect and was ignored; built-in rule was...

Hang on :) I re-visited [this comment](https://github.com/gitlabform/gitlabform/issues/388#issuecomment-1237280160) and tried that recipe. That worked! ```yaml ... 'very-silly-test-group-for-ldap-and-fun/test-project-2': merge_requests_approval_rules: inherit: false enforce: true default: approvals_required: 1 name: "All Members" rule_type: any_approver ```...

> (...) almost no callback plugin (except minimal) automatically dumps all task results if you don't provide -v. That's true for a regular playbook, but it's not true in case...