Skip to content

[v2] Merge v2 into lazy-plugin-initialization#10387

Merged
aemous merged 78 commits into
lazy-plugin-initializationfrom
pr/merge-v2-lazy-init-plugins
Jun 5, 2026
Merged

[v2] Merge v2 into lazy-plugin-initialization#10387
aemous merged 78 commits into
lazy-plugin-initializationfrom
pr/merge-v2-lazy-init-plugins

Conversation

@aemous
Copy link
Copy Markdown
Contributor

@aemous aemous commented Jun 5, 2026

Description of changes:

  • Merge v2 into lazy-plugin-initialization
  • (conflict resolution) Modify how plugin-load time is computed in benchmarking framework so that it works with lazy plugin loading. (latest 2 commits)

Description of tests:

  • Successfully passed all tests (see GitHub Actions).

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

RyanFitzSimmonsAK and others added 30 commits April 30, 2026 15:20
Co-authored-by: Prashant Bharti <bhartipr@amazon.com>
Co-authored-by: eodeyemi14 <84422131+eodeyemi14@users.noreply.github.com>
Rename get-resource-lf-tags.rst to list-lf-tags.rst
Add changelog for Python 3.14.5 upgrade
leezu and others added 22 commits June 2, 2026 10:53
…eice (#10358)

* Fall back to IPv6 for ec2-instance-connect ssh --connection-type eice

When --connection-type eice is set, resolve the destination address as
private IPv4 with IPv6 as a fallback, instead of unconditionally using
private IPv4. Without this, instances in IPv6-only subnets fail with
"Unable to find any IP address on the instance to connect to." even
though the EICE itself supports IPv6 destinations.

* Fall back to IPv6 for ec2-instance-connect open-tunnel

When --instance-id is given without --private-ip-address, resolve the
destination as private IPv4 with IPv6 as a fallback, instead of
KeyError'ing on PrivateIpAddress for instances in IPv6-only subnets.
The EICE accepts either address family.

Also raise a clear ParamValidationError when the instance has no IP
address at all (matching the ssh subcommand's behavior).
[V2] Replaced "CPU" with "Cpu" in Apprunner examples
Add a warning callout to the `aws cloudformation package` reference
documentation clarifying that the command treats the supplied template
as trusted build input. Paths referenced by template properties such as
CodeUri, ContentUri, TemplateURL, and the AWS::Include Location are
resolved against the local filesystem and uploaded to S3 using the
invoking user's AWS credentials and OS identity, with no constraint to
the template's directory. Users should not run the command against
templates from untrusted sources.

Co-authored-by: Roger Zhang <ruojiazh@amazon.com>
# Conflicts:
#	awscli/clidriver.py
#	awscli/plugin.py
@aemous aemous requested a review from a team June 5, 2026 19:08
@aemous aemous added v2 performance This PR or issue is related to performance. labels Jun 5, 2026
@aemous aemous requested a review from hssyoo June 5, 2026 19:11
@aemous aemous merged commit de59fc2 into lazy-plugin-initialization Jun 5, 2026
107 of 109 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

performance This PR or issue is related to performance. v2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants