feat(aws): support --aws-api=none to skip API Gateway setup - #937
Merged
Conversation
Allows deploying a Lambda function without provisioning or linking an API Gateway, for functions that are invoked directly or via other triggers. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
dominique-pfister
changed the title
--aws-api=none to skip API Gateway setup
tripodsan
approved these changes
Jul 23, 2026
adobe-bot
pushed a commit
that referenced
this pull request
Jul 23, 2026
# [14.3.0](v14.2.0...v14.3.0) (2026-07-23) ### Features * **aws:** support --aws-api=none to skip API Gateway setup ([#937](#937)) ([70dacbc](70dacbc))
|
🎉 This PR is included in version 14.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
noneas a valid value for--aws-api, allowing deployment of a Lambda function without provisioning or linking an API Gatewayhost,initApiId,createAPI,test,cleanUpIntegrations, andupdateLinksto short-circuit API Gateway operations when--aws-api=noneis setTest plan
helix-deploy --aws-api=noneagainst a test function and confirm no API Gateway is createdhelix-deploy --aws-api=nonedeploy succeeds and skips route linking--aws-api=auto|create|<id>flows are unaffected🤖 Generated with Claude Code