Skip to content

fix(gateway): use gateway ID instead of ARN for target polling#433

Merged
nborges-aws merged 1 commit intofeat/gatewayClientfrom
fix/gateway-target-arn-polling
Apr 23, 2026
Merged

fix(gateway): use gateway ID instead of ARN for target polling#433
nborges-aws merged 1 commit intofeat/gatewayClientfrom
fix/gateway-target-arn-polling

Conversation

@jesseturner21
Copy link
Copy Markdown
Contributor

Summary

  • get_gateway_target returns AccessDeniedException when called with a gateway ARN as gatewayIdentifier — it only accepts gateway IDs
  • create_gateway_target_and_wait, update_gateway_target_and_wait, and delete_gateway_target_and_wait were passing gatewayArn from the response directly to the polling call
  • Fixed by extracting the gateway ID from the ARN: response["gatewayArn"].rsplit("/", 1)[-1]
  • Added missing credentialProviderConfigurations to test_update_gateway_target_and_wait integ test (required by the API)

Test plan

  • All 15 integ tests pass with --order-scope=class
  • Verified get_gateway_target works with gateway ID but fails with ARN

get_gateway_target returns AccessDeniedException when called with a
gateway ARN. Extract the gateway ID from the ARN for all target
_and_wait polling methods. Also add missing credentialProviderConfigurations
to the update_gateway_target integ test.
@nborges-aws
Copy link
Copy Markdown
Contributor

niceeeeeeeee!

@nborges-aws nborges-aws merged commit b0e201a into feat/gatewayClient Apr 23, 2026
2 checks passed
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.

2 participants