Skip to content

Conversation

@YaroslavLitvinov
Copy link
Contributor

@YaroslavLitvinov YaroslavLitvinov commented Dec 29, 2025

  • Changed logic of adding config files to deployment: Now they added explicitly instead of deploying entire config folder (arguable)
  • Use cargo lambda --admerge merging lambda settings, particularly env vars added in Cargo.toml, .env file
  • Added back envs section to Cargo.toml, since it supports merge
  • lambda observability refactoring
  • otel collector config as a part of lambda
  • example of generic otel collector config, working with honeycomb
  • streaming, buffered goals added to makefile to set lambda invoke_mode from cli

Also moved config file of postgres queries crate to related readme

Copy link
Contributor

@DanCodedThis DanCodedThis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- Provide envs at deploy: `ENV_FILE=config/.env.lambda make deploy`

**Invoke mode** (Max response size up to 6 MB / 200 MB)
- `RESPONSE_STREAM` - Ensure you build with streaming feature `FEATURES=streaming make build deploy streaming`, otherwise it will not work
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

make deploy ... or make build deploy-only ... since deploy already includes build.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For sure build already includes deploy, but I wanted to explicitly show that this important for both build & deploy, since FEATURES=streaming is used on build step, then streaming goal is for deploy

@@ -0,0 +1,25 @@
receivers:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still shouldn't porabaly include this as a file, only in as readme exmaple.

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.

3 participants