Skip to content

fix(text): avoid trailing None for paginated response + scalar --query#10087

Open
mjfxjas wants to merge 2 commits intoaws:developfrom
mjfxjas:fix/cfn-describe-changeset-text-none-10061
Open

fix(text): avoid trailing None for paginated response + scalar --query#10087
mjfxjas wants to merge 2 commits intoaws:developfrom
mjfxjas:fix/cfn-describe-changeset-text-none-10061

Conversation

@mjfxjas
Copy link

@mjfxjas mjfxjas commented Feb 18, 2026

Fixes #10061.

When an operation is paginated, the text formatter previously applied --query per page. For scalar queries, if subsequent pages did not include the queried field, text output could include an extra trailing None line.

This change buffers the full paginated result before applying --query when using --output text, matching the behavior of the JSON/table formatters.

  • Adds a unit test covering the regression.

@mjfxjas
Copy link
Author

mjfxjas commented Feb 20, 2026

Friendly follow-up on this behavior fix.

This addresses trailing None output when using paginated responses with scalar --query, and keeps output consistent and clean for scripting use cases. If useful, I can add an additional regression test case in the preferred location.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Describing ChangeSet with '--output text' flag returns invalid result

1 participant

Comments