-
Notifications
You must be signed in to change notification settings - Fork 36
Comparing changes
Open a pull request
base repository: aws/aws-cdk-cli
base: [email protected]
head repository: aws/aws-cdk-cli
compare: [email protected]
- 6 commits
- 16 files changed
- 3 contributors
Commits on Jul 2, 2025
-
fix: CCAPI provider does not do pagination (#678)
The CCAPI provider stops after the first page of results. This may cause for example EC2 Prefix Lists that exist to not be found, if they don't occur in the first page of results. Make the provider retrieve all pages of results. Also in this PR: - New SDK mocks had been added without them being added to all the places where they needed to be added to be reset properly. Instead, put them all into an object so we can do a reliable `for` loop that will never go out of date again. - Up the `MaxResults` to 100, so we need to do fewer paginations and the chances of the error message finding too many elements has a reasonable indicator of the number of resources actually found. Fixes #587 --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Configuration menu - View commit details
-
Copy full SHA for f162c19 - Browse repository at this point
Copy the full SHA f162c19View commit details -
chore(cli): diff tests should not depend on message order (#680)
This turns into an error every time we add a new message to the ioHost. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Configuration menu - View commit details
-
Copy full SHA for 6a4d423 - Browse repository at this point
Copy the full SHA 6a4d423View commit details
Commits on Jul 3, 2025
-
chore(cli): telemetry sink (#585)
Introduces a generic telemetry sink to the cli. it is tested but not used anywhere. There are 3 base types of telemetry sinks: - `FileSink` -> gathers events and writes them to a file - `IoHostSink` -> gathers events and sends them to the IoHost (for writing to stdout/err) - `EndpointSink` -> gathers events and sends them to an external endpoint, batching at intervals of 30 seconds. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Configuration menu - View commit details
-
Copy full SHA for 4c14220 - Browse repository at this point
Copy the full SHA 4c14220View commit details -
chore(cli): cli type registry json (#682)
Pulling out of #631. This is relevant for telemetry but also helpful in general to compile the [dynamic] source of truth in `cli-config.ts` into a static json for our viewing pleasure. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Configuration menu - View commit details
-
Copy full SHA for 64d88d9 - Browse repository at this point
Copy the full SHA 64d88d9View commit details -
chore: make the environment deterministic for test stack (#684)
--- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Configuration menu - View commit details
-
Copy full SHA for 7b10fee - Browse repository at this point
Copy the full SHA 7b10feeView commit details -
fix(integ-runner): snapshots involving AZs are different if `enableLo…
…okups: false` (#685) In #666 we used `synthFast()` to always generate a snapshot in the same was as was used for validating (which was also using `synthFast()`). The difference being, that the context we load depends on the `enableLookups: false|true` flag that's passed to `new IntegTest()` in the test case itself. So when writing the snapshot we have to take that same field into account. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license
Configuration menu - View commit details
-
Copy full SHA for cf35f57 - Browse repository at this point
Copy the full SHA cf35f57View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff [email protected]@v2.1020.2