fix(docs): examples/extension-internal-flush: don't refer to a standalone layer arn for internal extension #980
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.
📬 Issue #, if available:
n/a
✍️ Description of changes:
Small tweak to the docs for our example on internal extensions. We currently refer to retrieving a layer arn from
cargo lambda deploy
. This was probably copy-pasted from other examples where we actually are callingcargo lambda deploy
with the--extension
target.In this case, we are deploying the function directly, and there is no standalone extension - it is all inside our primary binary.
Tweaking the language to remove a reference to a deployed layer ARN.
If we want to add a guide to invoking the remote function deployment, we could. The other examples don't have that though.
🔏 By submitting this pull request
cargo +nightly fmt
.cargo clippy --fix
.