Change description regex after aws lambda eni enhancement rollout #10331
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.
announcement (https://aws.amazon.com/blogs/compute/announcing-improved-vpc-networking-for-aws-lambda-functions/),
eni's created by lambda will now have a different description. This is not explicitly
documented, but was found in region 'eu-west-1', and will affect more regions over the next
few months as AWS rolls out this change. This description, which used to be a string of the
form "AWS Lambda VPC ENI: .*", now will look like this: "AWS Lambda VPC
ENI-xxx-xxxxxxx-xxxxx-xxxxxx-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx". As such, the regex used
to determine lingering lambda eni's no longer works in all regions, and in the future, when
this rollout is completed, will not work at all. This will appear to the user as a dependency
error, if they have any security groups attached to a lambda eni. For example:
Signed-off-by: Collin J. Doering collin@rekahsoft.ca
Community Note
Relates OR Closes #10044
Release note for CHANGELOG:
Output from acceptance testing: