-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ipsec p2 encryption-algorithm-option and hash-algorithm-option update seems disfunctional #69
Comments
wip ... fix-encalg-and-hashalg |
task args but
=> OK |
strange .. this works as expected - name: test
hosts: all
gather_facts: false
vars:
ikeid: 1
uniqid: eea1dcb2e051a
tasks:
- name: test del encryption-algorithm-option
delegate_to: localhost
community.general.xml:
path: cfg/ipsec-test1-04-encalg.xml
state: absent
pretty_print: true
xpath: "/opnsense/ipsec/phase2[ikeid='{{ ikeid }}' and uniqid='{{ uniqid }}']/encryption-algorithm-option" but not in the test setup |
|
seems we just have 2 options
|
In 5.1.1 lxml removed _ElementStringResult() currently I use: |
fck ... hours of debugging and testing for the a... ah... for nothing |
* encryption-algorithm-options fixed * hash-algorithm-options fixed * only delete hashalgopt if match is defined * test files for encalg and hashalg * issue #69 hash-algorithm-option fixed * issue #69 INTERIM hash-algorithm-option fixed * issue #69 doc hash-algorithm-option fixed * issue #69 restore original encryption-algorithm-option reset causing error * issue #69 fix encryption-algorithm-option reset * typo * issue #69 - working with lxml <= 5.1.0 * issue #69 - working with lxml <= 5.1.0 * issue #69 - updated test for fix-encalg-and-hashalg * issue #69 - cleanup fix-encalg-and-hashalg * issue #69 - use lxml 5.1.0 for tests * issue #69 - linted * Revert "issue #69 - updated test for fix-encalg-and-hashalg" This reverts commit 777fcc7. --------- Co-authored-by: Klaus Zerwes <[email protected]>
while starting some test implementation for #67 the 2 options let some ipsec tests fail ...
... or just deprecate the old legacy stuff and implement #42
The text was updated successfully, but these errors were encountered: