Open paulwinters-cenitex opened 4 years ago
I see the first call to ibmsecurity.isam.web.reverse_proxy.junctions.set() succee (interesting that force=True?). The second call to ibmsecurity.isam.web.reverse_proxy.junctions.set() has a number of values being passed as empty strings - default values are not kicking in? Why is that please?
We have a reverse proxy instance that is being created with two junctions. This is failing with a "The format of the request was not valid. The operation cannot be completed" error message when using ibmsecurity v2020.2.13.0.
We have it working correctly for a single junction.
The entrypoint of the playbook has this:
Which then calls 'lib/set_instance.yml':
Which then calls 'lib/set_junction.yml':
The working junction create:
The failing creation:
Versions are as follows: