-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Comparing changes
Open a pull request
base repository: localstack/localstack
base: main
head repository: CrisisTextLine/localstack-dev
compare: main
- 9 commits
- 52 files changed
- 2 contributors
Commits on Feb 17, 2026
-
Remove upstream LocalStack CI workflows (#2)
Keep only build-push-ghcr.yml for our Docker image builds.
Configuration menu - View commit details
-
Copy full SHA for c488eca - Browse repository at this point
Copy the full SHA c488ecaView commit details -
Add GitHub Actions workflow for building and pushing to GHCR (#3)
Multi-platform Docker build (amd64/arm64) triggered on push to main and manual dispatch.
Configuration menu - View commit details
-
Copy full SHA for bfb812c - Browse repository at this point
Copy the full SHA bfb812cView commit details -
Add deterministic IDs for EventBridge connections and API destinations (
#5) Generate reproducible resource IDs from md5(name) so that connection and API destination ARNs are predictable across container restarts. This enables hardcoded ARNs in init scripts for local development. Also fix mutable default bug in Connection and ApiDestination dataclasses where the id field was evaluated once at class definition time, causing all instances to share the same UUID.
Configuration menu - View commit details
-
Copy full SHA for ff16ab1 - Browse repository at this point
Copy the full SHA ff16ab1View commit details -
Bumps the cargo group with 1 update in the /tests/aws/services/lambda_/functions/rust-lambda directory: [tokio](https://github.com/tokio-rs/tokio). Updates `tokio` from 1.18.5 to 1.26.0 - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](tokio-rs/tokio@tokio-1.18.5...tokio-1.26.0) --- updated-dependencies: - dependency-name: tokio dependency-version: 1.26.0 dependency-type: direct:production dependency-group: cargo ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 24e6dec - Browse repository at this point
Copy the full SHA 24e6decView commit details -
Add Pipes service integration (#4)
Implement AWS EventBridge Pipes support with sources (SQS, Kinesis, DynamoDB Streams) and targets (SQS, Kinesis, API Destinations). Key components: - PipesProvider with all 10 API handlers (CRUD, start/stop, tagging) - PipeWorker poll loop reusing existing ESM pollers (1s default interval, configurable via PIPES_POLL_INTERVAL_SEC) - PipeEventProcessor with base64 data decoding matching AWS Pipes behavior - InputTemplate support with jsonpath and aws.pipes.* placeholders - API destination target with connection auth via SecretsManager - SQS target with FIFO support, Kinesis target with put_record - Stream poller fix for shard re-init on SequenceNumber errors
Configuration menu - View commit details
-
Copy full SHA for 019e15d - Browse repository at this point
Copy the full SHA 019e15dView commit details -
Configuration menu - View commit details
-
Copy full SHA for d8b4228 - Browse repository at this point
Copy the full SHA d8b4228View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4df2a61 - Browse repository at this point
Copy the full SHA 4df2a61View commit details -
Configuration menu - View commit details
-
Copy full SHA for e68b9c9 - Browse repository at this point
Copy the full SHA e68b9c9View commit details
Commits on Feb 20, 2026
-
fix: Fix Pipes API destination auth by matching secret key format (#6)
The _apply_connection_auth method expected PascalCase keys (e.g. BasicAuthParameters.Username) when reading from SecretsManager, but ConnectionService stores secrets using lowercase flat keys (e.g. {"username": ..., "password": ...}). This caused BASIC and API_KEY auth to silently fail with empty credentials.Configuration menu - View commit details
-
Copy full SHA for b68feeb - Browse repository at this point
Copy the full SHA b68feebView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...main