You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During investigation of #2837, @atieriannoted a case not covered by the fix. In the case of a schema with only custom operations and types, the @aws_iam annotation won't get automatically added to the custom type. E.g., in the following schema:
The transformed schema would correctly include @aws_iam on the getFoo field, but not on the Foo type itself, meaning that a properly authorized getFoo query would be unable to view the actual result.
There are a couple of notes to help gauge priority:
A workaround for this bug is to add a static auth rule to the field, which triggers the auth transformer to process the field:
Environment information
Data packages
Description
During investigation of #2837, @atierian noted a case not covered by the fix. In the case of a schema with only custom operations and types, the
@aws_iam
annotation won't get automatically added to the custom type. E.g., in the following schema:The transformed schema would correctly include
@aws_iam
on thegetFoo
field, but not on theFoo
type itself, meaning that a properly authorizedgetFoo
query would be unable to view the actual result.There are a couple of notes to help gauge priority:
A workaround for this bug is to add a static auth rule to the field, which triggers the auth transformer to process the field:
This does not pertain to custom operation fields that have scalar types: the below example works fine after the fix in fix: add aws_iam to custom operations when enableIamAuthorization is enabled #2921:
The text was updated successfully, but these errors were encountered: