• Joined on 2026-08-03
max commented on issue max/vmn-ansible#38 2026-09-17 18:09:53 +04:00
[FEATURE]: Immediate stop if an incorrect value is passed

Naming fixes are in place (93cee75), but password validation is just a copy-paste of hostname validation, password allows, in fact it requires, more complex combinations and special characters.…

max pushed to issue-38-stop-on-wrong-value at max/vmn-ansible 2026-09-17 18:00:21 +04:00
93cee75103 fix(task): minor names and typos fixes
max commented on issue max/vmn-ansible#38 2026-09-17 17:16:35 +04:00
[FEATURE]: Immediate stop if an incorrect value is passed

Tests with Alpine are passed. Minor naming fixes are necessary

max commented on issue max/vmn-ansible#38 2026-09-17 15:30:50 +04:00
[FEATURE]: Immediate stop if an incorrect value is passed

2fccf20768 updates VM deployment playbook, it uses shared validation pre_tasks and shares os_template and…

max pushed to issue-38-stop-on-wrong-value at max/vmn-ansible 2026-09-17 15:25:14 +04:00
24f34198ff feat(pb,role,task): makes VM deployment playbook use new validation pre_tasks, become_method and os_template tasks are shared now
max commented on issue max/vmn-ansible#38 2026-09-17 11:18:05 +04:00
[FEATURE]: Immediate stop if an incorrect value is passed

Since new tasks are highly modular, they can be used in VMs deployment as well. Although, slight renaming would be required to make the tasks independent of the guest type (VM or LXC). Also…

max pushed to issue-38-stop-on-wrong-value at max/vmn-ansible 2026-09-17 11:16:46 +04:00
f29de42397 feat(pb,role,task): generalize names of common pre_tasks and their variables, specifies LXC-specific ones
max opened issue max/vmn-ansible#39 2026-09-17 11:01:18 +04:00
[FEATURE]: final validation prompt
max commented on issue max/vmn-ansible#38 2026-09-17 10:56:39 +04:00
[FEATURE]: Immediate stop if an incorrect value is passed

Since new tasks are highly modular, they can be used in VMs deployment as well. Although, slight renaming would be required to make the tasks independent of the guest type (VM or LXC). Also…

max commented on issue max/vmn-ansible#38 2026-09-17 10:52:58 +04:00
[FEATURE]: Immediate stop if an incorrect value is passed

daa5826573 adds the requested support, but for LXCs only for now

max pushed to issue-38-stop-on-wrong-value at max/vmn-ansible 2026-09-17 10:51:31 +04:00
daa5826573 feat(pb,role,task): completes the LXC deployment workflow using new validation tasks
0696218eb6 feat(pb,task): moves input validation into separated tasks files. Play fails immediately if a validation fails
Compare 2 commits »
max created branch issue-38-stop-on-wrong-value in max/vmn-ansible 2026-09-17 10:51:30 +04:00
max commented on issue max/vmn-ansible#38 2026-09-16 18:17:38 +04:00
[FEATURE]: Immediate stop if an incorrect value is passed

Here is an example for hostname validation AND default value:

  tasks:
    - name: Set default hostname
      ansible.builtin.set_fact:
        lxc_hostname: "default-hostname"

    -…
max opened issue max/vmn-ansible#38 2026-09-16 18:05:40 +04:00
[FEATURE]: Immediate stop if an incorrect value is passed
max deleted branch issue-31-hostname-validation from max/vmn-ansible 2026-09-16 17:54:11 +04:00
max pushed to dev at max/vmn-ansible 2026-09-16 17:54:11 +04:00
4789bbd850 fix(pb): makes hostname validation strict enough
max closed issue max/vmn-ansible#31 2026-09-16 17:54:09 +04:00
[BUG]: hostname validation is incomplete
max merged pull request max/vmn-ansible#37 2026-09-16 17:54:09 +04:00
fix(pb): makes hostname validation strict enough
max created pull request max/vmn-ansible#37 2026-09-16 17:53:59 +04:00
fix(pb): makes hostname validation strict enough
max pushed to issue-31-hostname-validation at max/vmn-ansible 2026-09-16 17:52:07 +04:00
4789bbd850 fix(pb): makes hostname validation strict enough