Open shorbachuk opened 1 year ago
Please note this is working as designed in this release - safe is a required attribute needed to pass in: safe: description:
as stated in the doc: https://github.com/cyberark/ansible-security-automation-collection/blob/master/docs/cyberark_account.md
We may consider changing the behavior in the future release.
thanks.
required=true requires the safe to be present but it does not require non-null as per my example. Not asking to change the required=true behavior just asking to fix the malformed uri that results
Thanks for the clarification. You are absolutely right. We will add this to handle the malformed uri.
Hello Shorbachuk: Upon further review with our internal team, it seems to be an open issue with the Ansible platform itself when required is used. The discussion is here: https://github.com/ansible/ansible/issues/69190
if required, why allow someone to sent a none/empty value. This is definitely a debatable issue.
Will keep an open eye on this issue going forward.
What is there to monitor? That issue is closed. Also confirms the behavior is as I said. I’m a cyberark customer and would like this fixed as it’s clearly a bug
why allow empty safe? Because the api doesn’t require a safe when filtering
Summary
cyberark_account url is not properly url encoded when state=absent and safe is None.
I want to delete an account but I do not have the same name. The CyberArk API does not require a safe name.
Steps to Reproduce
Expected Results
Account is removed
Actual Results
Reproducible
Version/Tag number
1.0.19
Environment setup
Ansible 2.13
Additional Information
It seems the search_string is only properly encoded when the safe_filter is Not None
I believe Line 1087 should be