v4.0.1

Spectral Bot Update (GitHub & GitLab): Upgraded to version 2.2.0.
New Feature: The bot now supports handling GitHub synchronize events for pull requests, enabling scanning of code contributions during updates.

v4.0.0

Added

• Support to Gitlab bot deployment integration

Changed

• API gateway path

v3.0.0

Added

• Support to GitHub bot 2.x deployment integration
• Enable running multiple bot instances of the same type in a single region
• Enable setting a custom pattern for all the resources created by the module
• Enable setting a path to the lambda source code (Zip file)

Changed

• Lambdas runtime upgraded to node20.x

V2.1.0

GitLab bot: Add support in engines flag & scan configuration hardening

What's Changed

• Support hardening & engines flag by @ChengaDev in #12

Full Changelog: v2.0.0...v2.1.0

v2.0.0

BREAKING CHANGES:
GitLab integration infrastructure has been changed.
It is now using two lambda functions instead of one in order to return a response in less than 10 seconds which is the timeout limit for a webhook in GitLab.com (the timeout limit can be configured in a standalone GitLab server).

The first lambda starts up the integration, invokes the second lambda that does the scan, and after the invocation returns a response to GitLab.

v1.1.1 - Support secret manager in GitLab bot

In this version we added the option to pull the secrets required for the GitLab bot to accessed from AWS secrets manager.
In the future we are planning to add more vaults, and enable this option in more bots.

Gitlab & TFC integrations - new severities

This version contains new versions of Gitlab and TFC using new Spectral severities.

Versions update & Gitlab integration updates

This version contains:

1. Version updates (hashicorp/aws & terraform)
2. Gitlab integration updates

Add Jira & Gitlab integrations

v1.0.2

Enable Jira & Gitlab integrations

Drop layers and load download spectral as part of lambda execution

Drop layers and load download spectral as part of lambda execution