Skip to content
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

Update install to take provisioning tokens #15

Merged
merged 2 commits into from Jan 5, 2021
Merged

Update install to take provisioning tokens #15

merged 2 commits into from Jan 5, 2021

Conversation

shawndwells
Copy link
Contributor

No description provided.

@shawndwells
Copy link
Contributor Author

  • The documentation calls this an "installation token," however the CLI argument is "provisioning token," so used falcon_provisioning_token for variable name

@redhatrises
Copy link
Contributor

redhatrises commented Jan 4, 2021

@shawndwells since a provisioning token is optional and has to be enabled, should we require it for using and joining with the customer CID? This is my only question about this PR.

@shawndwells
Copy link
Contributor Author

@shawndwells since a provisioning token is optional and has to be enabled, should we require it for using and joining with the customer CID? This is my only question about this PR.

Tokens should not be required. Tried to reflect this in the code.

The command if there is no provisioning token:

  - name: CrowdStrike Falcon | Associate Falcon Sensor with your Customer ID (CID)
    command: "/opt/CrowdStrike/falconctl -s -f --cid={{ falcon_cid }}"
    when:
      - falcon_provisioning_token is not defined
      - falcon_cid
      - installed_sensor in ansible_facts.packages 

And here is the command if there is a provisioning token:

  - name: CrowdStrike Falcon | Associated Falcon Sensor with your Customer ID (CID) Using Provisioning Token
    command: "/opt/CrowdStrike/falconctl -s -f --cid={{ falcon_cid }} --provisioning-token={{ falcon_provisioning_token }}
    when:
      - falcon_provisioning_token
      - falcon_cid
      - installed_sensor in ansible_facts.packages

@redhatrises
Copy link
Contributor

@shawndwells since a provisioning token is optional and has to be enabled, should we require it for using and joining with the customer CID? This is my only question about this PR.

Tokens should not be required. Tried to reflect this in the code.

The command if there is no provisioning token:

  - name: CrowdStrike Falcon | Associate Falcon Sensor with your Customer ID (CID)
    command: "/opt/CrowdStrike/falconctl -s -f --cid={{ falcon_cid }}"
    when:
      - falcon_provisioning_token is not defined
      - falcon_cid
      - installed_sensor in ansible_facts.packages 

And here is the command if there is a provisioning token:

  - name: CrowdStrike Falcon | Associated Falcon Sensor with your Customer ID (CID) Using Provisioning Token
    command: "/opt/CrowdStrike/falconctl -s -f --cid={{ falcon_cid }} --provisioning-token={{ falcon_provisioning_token }}
    when:
      - falcon_provisioning_token
      - falcon_cid
      - installed_sensor in ansible_facts.packages

Got it... my eyes were blind. Thanks!

@redhatrises redhatrises merged commit 169109c into CrowdStrike:master Jan 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants