v2.7.1-rc

What's Changed

• feat: update sqs by @diego-dm-morais in #202
• bump version 2.7.1-rc by @ttamurajr in #203

New Contributors

• @diego-dm-morais made their first contribution in #202

Full Changelog: v2.7.0...v2.7.1-rc

v2.7.0

What's Changed

• Postgres startup delay config by @ttamurajr in #200
• chore: bump version to 2.7.0 by @ttamurajr in #201

Full Changelog: v2.6.0...v2.7.0

v2.6.0

What's Changed

• feat: storage facade by @Luis-Henrique in #180
• feat: add module to get object from cloud storage stream mode by @gabriel-f-santos in #181

New Features:

• Added a cloud storage module enabling retrieval of objects via Google Cloud Storage.
  

• Implemented a facade to retrieve storage objects based on the environment variable STORAGE_PROVIDER.
  

Messages Module:

Introduced a new facade module named storages to streamline the selection of storage providers.
The storages module dynamically selects the messaging provider based on the environment variable set:

•     For AWS environments, it utilizes S3 (Simple Storage Service).
  

•     For GCP environments, it utilizes Google Cloud Storage.
  

How to Use:

To select the storage provider, set the appropriate environment variable:

•     STORAGE_PROVIDER=s3 for AWS (S3).
  

•     STORAGE_PROVIDER=cloud_storage for Google Cloud Platform (Cloud Storage).
  

Full Changelog: v2.5.1...v2.6.0

v2.5.1

What's Changed

• fix: handle return pubsub by @gabriel-f-santos in #172
• chore: bump version 2.5.0 to 2.5.1 by @Luis-Henrique in #179

Full Changelog: v2.5.0...v2.5.1

v2.5.0

What's Changed

• feat: add messages module by @gabriel-f-santos in #158
• feat: add publish message function by @Luis-Henrique in #160
• feat: add pubsub to messages by @gabriel-f-santos in #166
• feat: add publish message batch to pubsub module by @Luis-Henrique in #164
• feat: add publish batch messages by @gabriel-f-santos in #167

New Features:

Added pubsub module to enable sending messages via Google Cloud Pub/Sub.
Implemented batch messaging capability for sending messages in bulk.

Messages Module:

Introduced a new facade module named messages to streamline messaging provider selection.
The messages module dynamically selects the messaging provider based on the environment variable set:
    For AWS environments, it utilizes SQS (Simple Queue Service).
    For GCP environments, it utilizes Google Cloud Pub/Sub.

How to Use:

To select the messaging provider, set the appropriate environment variable:
    MESSAGE_PROVIDER=sqs for AWS (SQS).
    MESSAGE_PROVIDER=pubsub for Google Cloud Platform (Pub/Sub).

New Contributors

• @Luis-Henrique made their first contribution in #163

Full Changelog: v2.4.0...v2.5.0

v2.4.0

Release Notes - Version 2.4.0

New Features

1. This version introduces a new module for Google Cloud Platform (GCP) token acquisition, providing a convenient way to generate short-lived ID tokens representing a service account. The primary purpose is to enable principals to obtain short-lived credentials for trusted service accounts and authenticate as the service account.

For more details, refer to the commit .

v2.3.3

What's Changed

• Fix Elastic APM agent issue reporting spindown of Lambda functions as an error.
  • fix: apm spindown issue for wrapped api handlers by @julianolf in #138
  • fix: apm spindown issue for wrapped sqs handlers by @julianolf in #139

Full Changelog: v2.3.2...v2.3.3

v2.3.2

What's Changed

• fix: name validation to match one character that is not a non-word character by @flaviacastro in #136

Full Changelog: v2.3.1...v2.3.2

v2.3.1

What's Changed

• fix: simplified logger exception call in the API module by @feliperails in #131

Full Changelog: v2.3.0...v2.3.1

v2.3.0

Release Notes - Version 2.3.0

New Features

1. Implemented functionality to capture response body for Elastic APM Python. The ELASTIC_APM_SANITIZE_FIELD_NAMES environment variable (https://www.elastic.co/guide/en/apm/agent/python/current/configuration.html#config-sanitize-field-names) can be used to sanitize fields with sensitive data.
2. Elastic APM request body changed to string. This is required for list-type request bodies to be compatible with ELK.
3. Added check to only set ELASTIC_APM_PROCESSORS if this environment variable is not set. This makes it possible to disable the ELK's default processors.

For more details, refer to the commit history.