-
Notifications
You must be signed in to change notification settings - Fork 59
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
4.6.0 fails #564
Comments
@TyraelTLK - I'll try to look into it later today - but that task will only run if you are using provisioning tokens? The conditional should fail if you are not passing in a token: - name: CrowdStrike Falcon | Master Image Prep | Set Provisioning Token (if applicable)
crowdstrike.falcon.falconctl:
cid: "{{ options.cid }}"
provisioning_token: "{{ options.provisioning_token }}"
state: present
when:
- falcon_remove_aid
- options.provisioning_token Can you debug that for me - specifically I'm interested in knowing the output of the following task in the - name: Checks if any options are set
ansible.builtin.set_fact:
any_option_set: "{{ true if (options | dict2items | selectattr('value', 'ne', omit) | list | length > 0) else false }}" |
Is this ok or do you need anything else? |
@TyraelTLK Can you try running against the latest changes in the git repo? Merged in the changes but want to make sure you are good before creating a new release. |
Hi, yes I can test it. I was FTO I'll send the result tomorrow |
#565 is working fine! |
Hi,
my pipeline that test the latest release of this collection started to fail with 4.6.0.
TASK [crowdstrike.falcon.falcon_configure : CrowdStrike Falcon | Master Image Prep | Set Provisioning Token (if applicable)] ***
fatal: [ksx-t6-debian12-postinstall.cos.is.keysight.com]: FAILED! => {"changed": false, "msg": "ERROR: "" is not valid value for checksum CID (CCID)"}
it is running with these variables:
"falcon_option_set": false,
"falcon_remove_aid": true,
"falcon_cid": ""
With these pipeline I'm checking just the package installation without activating the hosts.
I'm not sure what changes in 4.6.0 caused this and 4.5.2 worked fine.
The text was updated successfully, but these errors were encountered: