GraphQL schema compilation omits needed auth directives for nested types.

[BennettSmith]

Describe the bug
If I apply @auth to a model in my schema that uses nested types, during amplify push the schema compilation omits the @aws_iam @aws_cognito_user_pools directives for nested types that are more than one level deep.

Because of the omission, a GraphQL subscription for the owner of the Todo (authenticated via Cognito) from my iOS mobile app will fail when a Lambda function performs a mutation of the Todo when using credentials for an IAM role.

If I manually edit the schema using the AppSync Console to add the missing @aws_iam @aws_cognito_user_pools, then the subscription will work as expected.

Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system

To Reproduce
Create a new amplify app.
Use amplify auth add to add Cognito authentication.
Use amplify api add to add a GraphQL api. Choose the Todo sample schema. Select Cognito auto as the default. Then add IAM auth as well.
Edit the schema file to look like this:

type Todo @model @auth (rules: [
    { allow: owner }, 
    { allow: private, provider: iam, operations: [read] }
  ]) 
{
  id: ID!
  name: String!
  description: String
  author: Author
}

type Author
{
  firstName: String
  lastName: String
  address: Address
}

type Address
{
  street: String
  city: String
  state: String
  zip: String
}

With the updated schema, run amplify push --yes.

Expected behavior

I expect that the generated schema in build/schema.graphql will include the auth directives for all three nested types. It is only included for the Todo and Author. It should also be added to the Address.

Here is what I see generated:

type Todo @aws_iam @aws_cognito_user_pools {
  id: ID!
  name: String!
  description: String
  author: Author
  owner: String
}

type Author @aws_iam @aws_cognito_user_pools {
  firstName: String
  lastName: String
  address: Address
}

type Address {
  street: String
  city: String
  state: String
  zip: String
}

Here is what I expect to be generated:

type Todo @aws_iam @aws_cognito_user_pools {
  id: ID!
  name: String!
  description: String
  author: Author
  owner: String
}

type Author @aws_iam @aws_cognito_user_pools {
  firstName: String
  lastName: String
  address: Address
}

type Address @aws_iam @aws_cognito_user_pools {
  street: String
  city: String
  state: String
  zip: String
}

Desktop (please complete the following information):

• OS: MacOS 10.15.3
• Node Version. v12.16.2

[BennettSmith]

@nikhname Could you point me in the general direction of which part of the amplify-cli code I should look at to ferret out this issue? I'm keen to open a PR for this one. The bug is adding a manual step to each push we do, and when we forget the manual step it in turn causes our app to behave incorrectly.

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.