Include an optional SAM config file when deploying#946
Open
stephen-cox-nzx wants to merge 4 commits into
Open
Conversation
…t the SAM deploy command across mulitple lines for readability.
|
💚 CLA has been signed |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
🔍 Preview links for changed docs |
Author
|
Contributor Agreement: has now been signed |
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
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.
What does this PR do?
This PR:
example samconfig.yaml
Why is it important?
Deploying Elastic Serverless forwarder into a corporate environment requires compliance with corporate tagging standards. This change allows an easy way for users of this script to include tags into the created artifacts.
Checklist
CHANGELOG.mdand updatedshare/version.py, if my change requires a new release.Author's Checklist
How to test this PR locally
Related issues
Use cases
Deploying the serverless forwarder via the Direct approach, but automatically tagging the AWS resources it creates
Logs
(partial - as returned from by GitHub Action Workflow)