Stack Mapping Fails (V2 Transformer Migration)

[sacrampton]

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?

npm install -g @aws-amplify/cli

If applicable, what version of Node.js are you using?

v17.1.0

Amplify CLI Version

8.1.0

What operating system are you using?

AWS LINUX

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

Modified transform.conf.json

{
  "StackMapping": {
     "ItemclassificationResolver": "ConnectionStack2",
     "ItemlocationResolver": "ConnectionStack2",
     "ItemmaterialResolver": "ConnectionStack2",
     "ItemoperatingUnitResolver": "ConnectionStack2",
     "ItempackageResolver": "ConnectionStack2"
  }
}

Amplify Categories

api

Amplify Commands

push

Describe the bug

Trying to migrate existing database to the V2 transformer and the ConnectionStack.json exceeds 500 resources.

So modifying the transform.conf.json file to split into multiple ConnectionStacks.

I compiled the schema without any StackMapping first and extracted a list of 427 resources to put in the transform.conf.json file. I put them all in ConnectionStack2 as shown (partially below) - but when I compiled it comes back with the error that there are more than 500 resources in ConnectionStack2.

  "StackMapping":{
    "UomscaleResolver": "ConnectionStack2",
    "ScaleuomResolver": "ConnectionStack2",
    "ItemplantResolver": "ConnectionStack2",
    "PartbrandResolver": "ConnectionStack2",
    "PhotoitemResolver": "ConnectionStack2"
   }

So I spread the resources across 6 additional Connection Stacks and that compiled fine - but when I push I get the following error.

Circular dependency between resources: [CustomResourcesjson, ConnectionStack6, ConnectionStack2, ConnectionStack3, ConnectionStack4, ConnectionStack5]

The Custom Resources is attached - there are no custom resources.
CustomResources.zip

Alternately, if I then change up the StackMapping to get beyond the error above, namely by reducing the numbers of records in StackMapping or changing how they are mapped I can get beyond the above circular error - but then I'll get the following error saying it failed...

CREATE_FAILED AssetVisitseriesReferenceResolver AWS::AppSync::Resolver Tue May 10 2022 23:18:22 GMT+0000 (Coordinated Universal Time) Only one resolver is allowed per field. (Service: AWSAppSync; Status Code: 400; Error Code: BadRequestException; Request ID: 8cf3287a-6301-4222-874c-6f42cfbcf62c; Proxy: null)

Expected behavior

Expect it to work as per V1 where I put any resource from the original ConnectionStack.json into the StackMapping table and that resource moves to the separate json file. This is not the case as evidenced by my addition of 423 resources exceeds the 500 limit in the ConnectionStack2.json

Reproduction steps

See above

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information

No response

[sacrampton]

This issue aws-amplify/amplify-cli#9762 is very similar and lots of people in this thread were reporting the same issue.

aws-amplify/amplify-cli#9762 (comment)
aws-amplify/amplify-cli#9762 (comment)

[sacrampton]

Hi @edwardfoyle - you mentioned this in your comment aws-amplify/amplify-cli#9762 (comment) - but I've tried for quite some time and there seems to be no way to get this working.

In V1 if I put 200 resources in StackMapping to go to say ConnectionStack2 then there are exactly 200 resources placed in ConnectionStack2 - but V2 is doing something substantially different with StackMapping. For example above, I put 427 into StackMapping - but it generates more than 500 resources into ConnectionStack2.

Something seems to be really messed up with the way StackMapping is generating the stacks. For example, if you split the same resource up between different stacks you can get different failure results.

If you follow the instructions it just doesn't work.

Once again, this is another show stopper from moving to V2.

[sacrampton]

Here is an example - there are 100 entries in the StackMapping for ConnectionStack2 and the compile generates 227 resources. Its adding all the functions in the stack in addition to the records I entered.

[sacrampton]

Hi @josefaidt - just wanted to follow up on this one. The documentation (https://docs.amplify.aws/cli/graphql/override/#place-appsync-resolvers-in-custom-named-stacks) for this does not appear to be accurate.

[sacrampton]

Hi @alharris-at - any thoughts on this issue?

[sacrampton]

Hi @alharris-at @josefaidt - any thoughts on this issue over the last couple of weeks. This is a roadblock to be able to migrate a production (ie. large) database to the V2 Transformer.

[josefaidt]

Hey @sacrampton 👋 apologies for the delay here!! I've promoted this with the team to look into a bit deeper but this is something we are actively investigating! Sorry for not posting an update sooner

[josefaidt]

@sacrampton in your transform.conf.json file I noticed the StackMapping keys are not prefixed with the operation (<Get | List | Create | Update | Delete><model name>Resolver).

  "StackMapping":{
    "UomscaleResolver": "ConnectionStack2",
    "ScaleuomResolver": "ConnectionStack2",
    "ItemplantResolver": "ConnectionStack2",
    "PartbrandResolver": "ConnectionStack2",
    "PhotoitemResolver": "ConnectionStack2"
   }

Are these the relational resolvers you're attempting to extract to their own stack?

Looking at a sample schema where we have a Todo model, if I specify the following in my transform.conf.json file:

{
  "Version": 5,
  "ElasticsearchWarning": true,
  "transformers": [],
  "StackMapping": {
    "CreateTodoResolver": "MyCustomStack"
  }
}

And run amplify api gql-compile, we see the Create* resolver is split out of build/stacks/Todo.json and into build/stacks/MyCustomStack.json

[sacrampton]

Hi @josefaidt

I've included the full transform.conf.json with this link below.

transform.conf.zip

Using "amplify api gql-compile --minify" the GraphQL Schema successfully compiled.

But when I do the push "amplify push --no-gql-override --yes" it fails with this error.

UPDATE_FAILED               apidatastore2                AWS::CloudFormation::Stack Wed Jun 01 2022 04:19:19 GMT+0000 (Coordinated Universal Time) Circular dependency between resources: [Company, EquipmentReferenceAttribute, SearchableStack, Photo, Document, GlobalPickList, Item, Classification, ProcessingQueue, Asset, M2MConnection, Bom, BrandSynonym, Messages, CustomResourcesjson, CrowdQueue, Brand, QuarantineArea, Part, ExternalCharacteristicValue, Package, OrgRole, CrowdResults, ProcessingQueueErrors, Group, User, ConnectionStack2, ConnectionStack3, OperatingUnit, ConnectionStack4, ConnectionStack5, Risk, EquipmentReference, FailureMode, FieldList, PotentialResult, FieldSet, Plant, ClientPickList, Defect, Division, PartsList, Component, AssetVisit, Submission, DefectMedia, Material, Scale, AssetVisitAttribute, OperatingGroup, CrowdSourcingJob, Series, Uom, CrowdWorker, ExternalAsset, CharacteristicValue, PhotoButton, Location]