Release Highlights
Release tag: v1.2.0
This release includes a single configuration change that allows deploys to specify the location of the queues that hold input for the crawler.
Upgrade Notes
No Action Required. Optionally, you can set a configuration to control where input queues will be constructed.
What’s changed
Changes: v1.1.0..v1.2.0
Minor Changes
Configure location of queues
- Make Crawler queue in Azure separate from Azure results storage (#591) (@ljones140)
Release v1.2.0 adds the support of running Crawler queues in a separate Azure
account as the results storage blobs.
Requirement came from organizations that want to submit results to clearlydefinedprod Azure but don't want to have the queues in the same Azure account.
The crawler configuration takes an additional env var CRAWLER_QUEUE_AZURE_CONNECTION_STRING
If provided the crawler will use this storage account for the queues.
If not provided it will use same connection defined in CRAWLER_AZBLOB_CONNECTION_STRING
Bug Fixes and Patches
- docs: add SECURITY.md (#584) (@nickvidal)
- Add separate job for testing Docker build (#580) (@lumaxis)
