Skip to content

Conversation

@jkruse14
Copy link

Issue #, if available:
N/A

Description of changes:
Adds an optional parameter to the CloudFormation stack to be able to specify a FunctionName when installing with the SAM CLI. The README is updated with CI/CD (non-guided) instructions including how to specify the parameter-override for the FunctionName


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

1. Make sure docker is running
2. Navigate to `guard-lambda` directory and run `sam build --use-container` to build the code for the Lambda function
3. Run `sam deploy --guided` and complete the interactive workflow. This workflow will create a CloudFormation changeset and deploy it
4. Once it succeeds, the name of the function will be shown in the `CloudFormationGuardLambdaFunctionName` output
Copy link
Contributor

Choose a reason for hiding this comment

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

If we are asking user to pass a parameter for name this line will change, correct?

Copy link
Author

Choose a reason for hiding this comment

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

If a samconfig.toml is not being used, you are correct. sam deploy will need this added. I will update the PR.

Copy link
Author

Choose a reason for hiding this comment

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

I misunderstood - no, I don't think this will need to change. The output does not change by having a stack parameter. Also, if following the guided approach, it should be managed through the interactive process. The parameter is not required, so already existing consumers will not need to add it.

@joshfried-aws
Copy link
Contributor

Hi @jkruse14 I was wondering if you are able to look at the comments @akshayrane has left when you have a moment.

Thanks

@jkruse14 jkruse14 requested a review from akshayrane March 22, 2024 20:35
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