Skip to content

ci: publish durable execution lambda layer (EXPERIMENTAL)#493

Draft
zhongkechen wants to merge 5 commits into
mainfrom
codex/lambda-layer-publish
Draft

ci: publish durable execution lambda layer (EXPERIMENTAL)#493
zhongkechen wants to merge 5 commits into
mainfrom
codex/lambda-layer-publish

Conversation

@zhongkechen

Copy link
Copy Markdown
Contributor

Summary

  • add a GitHub workflow to build and publish public Lambda layer versions for the SDK + OTel plugin
  • add a repo script for building runtime/architecture-specific layer zips
  • document manual and release-driven layer publishing

Testing

  • hatch fmt --check .github/scripts packages/aws-durable-execution-sdk-python-otel
  • hatch run test:all .github/scripts/tests/test_build_lambda_layer.py .github/scripts/tests/test_parse_sdk_branch.py packages/aws-durable-execution-sdk-python-otel/tests
  • hatch run types:check
  • hatch build (OTel package)
  • python3 .github/scripts/check_dist_legal_files.py packages/aws-durable-execution-sdk-python-otel
  • workflow YAML parse check

@zhongkechen zhongkechen changed the title ci: publish durable execution lambda layer ci: publish durable execution lambda layer (EXPERIMENTAL) Jun 26, 2026
name: Publish Lambda Layer

on:
pull_request:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

this just for testing?

rather than triggering on release?


permissions:
contents: read
id-token: write

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

it doesn't really matter all that much given there's only 1 job in here currently, but generally the pattern we follow is read at the top level and write only on the jobs that need it.

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.

2 participants