Skip to content

fix: use the correct content property for Lambda Layer Version#3552

Merged
moelasmar merged 2 commits intoaws:developfrom
moelasmar:develop-fix-lambda-layer-content-property
Dec 29, 2021
Merged

fix: use the correct content property for Lambda Layer Version#3552
moelasmar merged 2 commits intoaws:developfrom
moelasmar:develop-fix-lambda-layer-content-property

Conversation

@moelasmar
Copy link
Contributor

Which issue(s) does this change fix?

use the correct content property for Lambda Layer Version

Checklist

  • Add input/output type hints to new functions/methods
  • Write design document (Do I need to write a design document?)
  • Write unit tests
  • Write/update functional tests
  • Write/update integration tests
  • make pr passes
  • make update-reproducible-reqs if dependencies were changed
  • Write documentation

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

@github-actions github-actions bot added area/build sam build command pr/internal labels Dec 29, 2021
@moelasmar moelasmar requested a review from mndeveci December 29, 2021 20:45
@moelasmar moelasmar merged commit 279ba2e into aws:develop Dec 29, 2021
@moelasmar moelasmar deleted the develop-fix-lambda-layer-content-property branch December 29, 2021 21:11
mndeveci pushed a commit to mndeveci/aws-sam-cli that referenced this pull request Apr 5, 2022
)

* fix Lambda LayerVersion resource content property

* add integration test case
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/build sam build command pr/internal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants