pulumi-aws
pulumi-aws copied to clipboard
experiment to understand ci speed
Does the PR have any schema changes?
Does the PR have any schema changes?
Looking good! No breaking changes found. No new resources/functions.
Maintainer note: consult the runbook for dealing with any breaking changes.
Is README.md missing any configuration options?
assumeRoleWithWebIdentity not found in Configuration section
customCaBundle not found in Configuration section
defaultTags not found in Configuration section
ec2MetadataServiceEndpoint not found in Configuration section
ec2MetadataServiceEndpointMode not found in Configuration section
httpProxy not found in Configuration section
httpsProxy not found in Configuration section
ignoreTags not found in Configuration section
noProxy not found in Configuration section
retryMode not found in Configuration section
s3UsEast1RegionalEndpoint not found in Configuration section
sharedConfigFiles not found in Configuration section
skipRequestingAccountId not found in Configuration section
stsRegion not found in Configuration section
tokenBucketRateLimiterCapacity not found in Configuration section
useDualstackEndpoint not found in Configuration section
Please add a description for each of these options to README.md. Details about them can be found in either the upstream docs or schema.json.
3m:32s prerequisites job possible on the warm cache it seems: https://github.com/pulumi/pulumi-aws/actions/runs/8445164030/job/23132412156
Closing, most of this has been upstreamed to ci-mgmt and the bridge. We can still try to remove P=2 compilation parallelism limits that were there to limit RAM use, though it may be tricky.