Skip to content

Conversation

@whummer
Copy link
Member

@whummer whummer commented Jan 24, 2026

Add comprehensive proxy tests for AWS AppSync.

Note 🤖 : Tests have been generated via an AI agent (Claude Code).

Changes:

  • GraphQL API CRUD operations
  • API key management
  • Schema creation and introspection
  • Data source operations
  • Read-only proxy mode
  • Operations-based filtering

Uses fixture-based cleanup to ensure no AWS resources are left behind.

whummer and others added 3 commits January 24, 2026 20:05
Add comprehensive proxy tests for AWS AppSync covering:
- GraphQL API CRUD operations
- API key management
- Schema creation and introspection
- Data source operations
- Read-only proxy mode
- Operations-based filtering

Uses fixture-based cleanup to ensure no AWS resources are left behind.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add retry around put_record call as Kinesis streams may need a brief
moment after reporting ACTIVE status before they can accept writes.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@whummer whummer marked this pull request as ready for review January 26, 2026 16:11
Copy link
Contributor

@nik-localstack nik-localstack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tests look good 🙌

One interesting observation about appsync operations

There are (at least) two operations that would incorrectly identified as WRITE requests by our logic :

Not sure if we want modify the aws_proxy.server.aws_request_forwarder.AwsProxyHandler._is_read_request in this PR to have better read-only support of the service.

I think It would be great if the agent would be able to "catch" these and improve the read-only support in general, maybe we could re-iterate on the AGENTS.md instructions to make it happen?

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.

3 participants