T7940 will require implementing this. I don't think I would be able to implement this all by myself and will need some guidance.

Ok so this can by worked around by running set terminal key query-help disable is operation mode.

@Viacheslav I will need some help with making configuration migrations. Since it seems for this we will need to make significant changes to the commit-archive options since right now it uses a leafNode. I do have a somewhat hacky option to allow &subdir=path/to/subdir inside the url.

@Viacheslav I need some guidance. I am trying to figure out what validator to use and it seems that the file-transport and url validators aren't in the vyos-1x repo and I can't seem to figure out what they are actually pointing to.

This could be done with systemd-cryptenroll and LUKS while bound to a TPM. Also you could bind it to a PKCS11 token (Yubikey) with a no touch and no pin policy to allow auto booting. (Not recommending FIDO2 because it always requires user presence)

acme.sh sounds like it would be a good fit. I definitely would want to have this added.

This would be dhcp-requested-address though I think adding it might cause other issues. Especially if the requested address is already used.

Seems this should be closed.

Documentation PR has been created https://github.com/vyos/vyos-documentation/pull/1708

https://github.com/vyos/vyos-1x/pull/4852 is ready. I just need to add to the documentation.

I will add this along with touch-required

https://github.com/vyos/vyos-1x/pull/4851 here's the PR

https://github.com/scj643/vyos-1x/tree/git-archive-subdir the branch I have for my changes to add this.

I will take a look into this.

This is an apt error and unrelated to VyOS build

PR https://github.com/vyos/vyos-1x/pull/1305

https://github.com/vyos/vyatta-config-mgmt/blob/current/scripts/vyatta-commit-push.pl#L71-L82 seems to be the root cause for this.

Opened https://github.com/vyos/vyos-1x/pull/1083 which fixes this issue

I have a fix that will make it send a single item list and pass the validation check

Ok thanks for clarifying that.

@SrividyaA What was the reason for adding (missing useful functionality) to the issue type? This is useful if you are in a dual wan environment with a DOCSIS cable modem that is failing, which will attempt to give you a DHCP lease on 192.168.100.0/24

This issue seems to have gone away or I haven't noticed it recently.

This seems to also happen with setting dhcpv6 as well.

This also happens if you delete ipv6 address autoconf and commit. Where it will drop all IP addresses besides the target interface's.