Skip to main content

Trigger scans in Informer via your CI/CD pipeline

Project description

Informer.io Scan Trigger Library

This library is designed to trigger scans in the Informer.io platform. It supports automated workflows by allowing users to initiate scans programmatically using an API key, an optional test UUID, and a list of assets. Features

API Key Authorization: Securely trigger scans using an API key.
Optional Test UUID: Specify a test UUID for targeted scanning.
Asset List Scanning: Initiate scans on a list of specified assets.
Error Logging: Errors and failures are logged for troubleshooting, without halting execution.

Setting Up the Environment:

To use the library, you need to provide an API key. You can pass this as a command-line argument or set it as an environment variable.

export INFORMER_API_KEY=your-api-key

Triggering a Scan

  1. Using Command-Line Arguments

You can pass the API key, an optional TEST_UUID, and a list of assets directly as arguments:

triggerInformerScan --api_key your-api-key --assets "a.b.com,b.com,example.com"

Optionally, you can include a TEST_UUID. Scans will then start on both the assets in the test and the named assets:

triggerInformerScan --api_key your-api-key --test_uuid your-test-uuid --assets "a.b.com,b.com,example.com"
  1. Using Environment Variables

If INFORMER_API_KEY is set, you can trigger the scan by just providing the assets:

bash

triggerInformerScan --assets "a.b.com,b.com,example.com"

And optionally the TEST_UUID:

triggerInformerScan --test_uuid your-test-uuid --assets "a.b.com,b.com,example.com"

Limitations

Frequency of Scans: Only one "once" scan can be triggered per 24-hour period per asset or test.
Error Reporting: Errors are reported through logs and do not halt the script execution.

Finding the Test UUID

If you have a specific test in Informer.io for which you want to trigger a scan:

Navigate to the test detail pane in the Informer.io platform.
Locate the UUID, uniquely identifying each test.
Use this UUID with the library for targeted scanning of related assets.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

trigger_informer_scan-0.2.tar.gz (3.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

trigger_informer_scan-0.2-py3-none-any.whl (4.4 kB view details)

Uploaded Python 3

File details

Details for the file trigger_informer_scan-0.2.tar.gz.

File metadata

  • Download URL: trigger_informer_scan-0.2.tar.gz
  • Upload date:
  • Size: 3.7 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.0.0 CPython/3.10.12

File hashes

Hashes for trigger_informer_scan-0.2.tar.gz
Algorithm Hash digest
SHA256 93c9d9024787e131ed7650df46c923f0a84d106433d4fee7f51b77c5e014900c
MD5 39b6c34411533c59ad56ccda690bac62
BLAKE2b-256 9ddabf734f119e7926e29f1d1a7e78417d8a3cf5cad2aef5b88e2d1a35b1587d

See more details on using hashes here.

File details

Details for the file trigger_informer_scan-0.2-py3-none-any.whl.

File metadata

File hashes

Hashes for trigger_informer_scan-0.2-py3-none-any.whl
Algorithm Hash digest
SHA256 42dfa69b8258e4b0b4d48da213c512b36b929f25cc9aae88c69a7e9c66b61cad
MD5 67beabc9ab5017ff89344e85d5e741ae
BLAKE2b-256 c44d4b9ea7b068c89e36daa480d1d2594b390cded26683731bfe4d0e06929b36

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page