Cannot perform more than one GSI creation or deletion in a single update; ConnectionStack failed to update

** Which Category is your question related to? **
graphql transformer
** What AWS Services are you utilizing? **
Amplify
** Provide additional details e.g. code snippets **
I change my annotated schema.graphql:
type Item @model {
   price: Int
   status: String
   measurement: String
+  inventory: Inventory @connection(name: "InventoryItems")
 }

 type Inventory @model {
   id: ID!
   name: String!
-  items: [Item] @connection
+  items: [Item] @connection(name: "InventoryItems")
   users: [InventoryMembership] @connection(name: "InventoryMembership_Inventory")
 }

which causes change to compiled schema.graphql:
type Item {
   price: Int
   status: String
   measurement: String
+  inventory: Inventory
 }

input CreateItemInput {
   price: Int
   status: String
   measurement: String
-  inventoryItemsId: ID
+  itemInventoryId: ID
 }

input UpdateItemInput {
   price: Int
   status: String
   measurement: String
-  inventoryItemsId: ID
+  itemInventoryId: ID
 }

amplify push results in below errors. See full log.

Cannot perform more than one GSI creation or deletion in a single update"

From https://github.com/aws-amplify/amplify-cli/issues/82#issuecomment-434016373, I should be good since my change only involves 1 connection (item-inventory). Why the problem and how to resolve this? @mikeparisstuff Thank you!

As a follow-up, after a failed push attempt, no matter what change I make to the annotated schema.graphql, all pushes fail with below error: https://gist.github.com/YikSanChan/84663256309e9756e4aec1f693870b81.
Even worse, even though all pushes fail, one of my AppSync API stops working.
query listItems2{
  getInventory(id:"befeb059-712f-4a1a-9999-6759b8fa812b") {
    items {
      items {
        name
      }
    }
  }
}

It returns below null rather than all connected items of the inventory (the previous behavior).
{
  "data": {
    "getInventory": {
      "items": null
    }
  }
}

FYI, this is request/response template mapping for getInventory.
# request template mapping
{
  "version": "2017-02-28",
  "operation": "GetItem",
  "key": {
      "id": $util.dynamodb.toDynamoDBJson($ctx.args.id)
  }
}

# response template mapping
$util.toJson($context.result)

Any help?

Cannot wait too long :( So I simply amplify api remove && amplify push to delete the whole api and its data, and restart from scratch.
This is not ideal but since I am still in dev so it is fine for now. Look forward to having mature solution

Doing the same as @YikSanChan, encountered issue when went from an Unnamed Connection to a Named Connection. Good that we are just in dev, this would be really frustrating if was encountered later on.

as a follow-up note to this, the GSI which does get created will not roll back, and then a subsequent push attempt will cause a different failure.

Unfortunately this is a limit in DynamoDB that we must work around. In general, we will be providing new ways to customize what indexes exist on a table and enabling you to use these indexes with @connection. This way you can change the name of the connection fields without impacting the underlying GSI itself. If you are stuck in a situation where a GSI cannot be created nor destroyed via CloudFormation, I would suggest going to the CloudFormation console to manually remove the GSI that you no longer need.

@mikeparisstuff I am facing the same problem as described here, may be it possible to detail more how to
"manually remove the GSI that you no longer need." ?

why is this marked as a feature-request and not a bug? I'm having the same issue where I wanted to add a sortField to my connection, and having done a few changes then the push will always failed. I had to to the same as @YikSanChan and remove the api and push it again losing all my data.

Having the same problems as well while building out a fairly complex schema. Luckily we have not moved to production yet, but this has slowed development.

same issue. using the amplify api remove && amplify push solution, can we get some eyes on this bug?

why is this marked as a feature-request and not a bug?

From our perspective, this is indeed a critical bug. It makes working with more than one person on a real-world project using @connection and CI/CD impossible and rendering the whole framework potentially unfit for production usage.

@jordanranz @mikeparisstuff This is a major issue for us this changes our deployment time from 8 minutes to n number of connections times 8 minutes then multiplied by the number of environments we have. This is a massive time sink for us. Is there at least a script we can run to manage the schema deployment without a refactoring on Amplify's end?

I would vote for this as a critical bug, considering the following use-case I am currently experiencing:
Making the following schema additions:
type Organization{
subscriptions: [Subscription] @connection(name: "OrganizationSubscriptions")
...
}

type Subscription{
organization: Organization @connection(name: "OrganizationSubscriptions")
...
}

If I try and add 1 connection at a time, it fails to compile the schema (missing the associated named-connection on the other object).
If I try and add them both at the same time, I get the Resource is not in the state stackUpdateComplete
I am totally blocked by this bug, with my only other option being deleting and recreating my API.

If you are stuck in a situation where a GSI cannot be created nor destroyed via CloudFormation, I would suggest going to the CloudFormation console to manually remove the GSI that you no longer need.

@mikeparisstuff Is this as simple as going to the nested stack for each of the respective models and removing the corresponding item in the GlobalSecondaryIndexes array? I would assume that's accompanied by the removal of the @connection directive for each model within your repository's schema file.
Could you confirm / elaborate on this?

In agreement with @mhrisse , after having developed our application around Amplify, we are terrified to launch our production environment because the framework is proving to be terribly unreliable, hard to change, underdocumented, and there is a push to add new functionality instead of fixing critical bugs in existing / core functionality. A lot of the promises made by Amplify should have the caveat: "unless something goes wrong, in which case you are in serious trouble". For instance, "Amplify makes adding an API easy, unless something goes wrong in case you are in serious trouble and have to delete your API + data + relaunch your API."

@ajhool, we’re aware of the this issue and haven’t been ignoring this. We have been actively discussing & designing short and long term resolutions internally. This issue is tied to the updating of the @connections directive causing Cloudformation Update failures. You would encounter this error because of a limit in the DynamoDB service which doesn’t allow you to create or update or delete more than 1 GSI at a time. It is a difficult problem to workaround, but we’re looking into ways to get around this and will soon be introducing Custom Indexes (#1463) as the first step towards getting around this issue.
As @mikeparisstuff mentioned, the workaround for now is to carefully update your @connections whenever you’re doing so. For now, when you make changes to @connection fields that will impact the underlying index, make the changes in two steps. First remove the existing @connection field and push your project. Then add back the connection field with the new configuration and push your project again.
In addition, as a first step we’ll be adding a note in our official docs around modifying @connections. We are also planning to add additional validations to the CLI push command. These will check your annotated schema before we push the schema to the cloud to prevent situations like this. Lastly, with the upcoming launch of custom indexes (#1463), customers can bypass this issue by managing their indexes (GSIs) themselves instead of the CLI managing it for them.

Please do not get me wrong, we really appreciate the effort everyone is puting into Amplify.
From a product management perspective, this @connection workaround (plus 1. missing rock solid @function functionality and 2. a bad taste about putting complex if-the-else logic AVT) just adds to the taste that is just not feasible to use this in a real-world team yet.
When you are building a complex product, the last thing you want to worry about is someone removing a connection is trashing everyones environment, while developer are already waiting a lot for the cloud to provision simple tings like adding a field, because of missing offline functionality. (3. offline)
I am confident Amplify is going to be great product or framework, it might just not be ready for prime time for those of us who are betting their business or start-up on this. Good things take time, all frameworks I have worked with in the past 25 years had these growing up pain.

I got a long schema definitions out of that one filed 'type' initially set as string
type VarietyAttachment @model @searchable {
	varietyAttachmentId: ID!
	variety: VarietyMain @connection(keyField: "varId")
	year: String
	country: MasterLocation @connection(keyField: "locationId")
	report: MasterReport @connection(keyField: "reportId")
>>>>>>  type: String
	description: String
	createdBy: UserMain @connection(keyField: "createdUserId")
	updatedBy: UserMain @connection(keyField: "updatedUserId")
	createdAt: String
	updatedAt: String
	spadAttachment: [String]
}

Now I need to change that that to a connection type
type VarietyAttachment @model @searchable {
	varietyAttachmentId: ID!
	variety: VarietyMain @connection(keyField: "varId")
	year: String
	country: MasterLocation @connection(keyField: "locationId")
	report: MasterReport @connection(keyField: "reportId")
>>>>>>  type: MasterAttachType @connection(keyField: "attachTypeId")
	description: String
	createdBy: UserMain @connection(keyField: "createdUserId")
	updatedBy: UserMain @connection(keyField: "updatedUserId")
	createdAt: String
	updatedAt: String
	spadAttachment: [String]
}

which ended up in error
Following resources failed

× An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete

After amplify push following activities happened
- Updating resources in the cloud. This may take a few minutes...

 This may take a few minutes...

 This may take a few minutes...

UPDATE_ROLLBACK_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyNote-7M3L6HT5JFZG AWS::CloudFormation::Stack Sat Jun 15 2019
19:40:43 GMT+0530 (India Standard Time) User Initiated
UPDATE_IN_PROGRESS          UpdateVarietyNoteResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019
19:40:46 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS          GetVarietyNoteResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019
19:40:46 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS          CreateVarietyNoteResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019
19:40:46 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS          DeleteVarietyNoteResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019
19:40:46 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS          ListVarietyNoteResolver                                                   AWS::AppSync::Resolver     Sat Jun 15 2019
19:40:47 GMT+0530 (India Standard Time)
UPDATE_COMPLETE             CreateVarietyNoteResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019
19:41:13 GMT+0530 (India Standard Time)
UPDATE_COMPLETE             UpdateVarietyNoteResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019
19:41:13 GMT+0530 (India Standard Time)
UPDATE_COMPLETE             GetVarietyNoteResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019
19:41:18 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

 This may take a few minutes...

 This may take a few minutes...

UPDATE_COMPLETE                              DeletevarietySprHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:52 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              ListvarietySprHistoryResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdatevarietySprHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetvarietySprHistoryResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:10 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreatevarietySprHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:15 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-varietySprHistory-18O7KG7ZU6915 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:16 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE DeleteVarietyProfileResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:01 GMT+0530 (India Standard Time)
UPDATE_COMPLETE CreateVarietyProfileResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:03 GMT+0530 (India Standard Time)
UPDATE_COMPLETE ListVarietyProfileResolver   AWS::AppSync::Resolver Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_COMPLETE UpdateVarietyProfileResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:15 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE ListMasterTraitResolver   AWS::AppSync::Resolver Sat Jun 15 2019 19:40:50 GMT+0530 (India Standard Time)
UPDATE_COMPLETE UpdateMasterTraitResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:40:51 GMT+0530 (India Standard Time)
UPDATE_COMPLETE CreateMasterTraitResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:06 GMT+0530 (India Standard Time)
UPDATE_COMPLETE GetMasterTraitResolver    AWS::AppSync::Resolver Sat Jun 15 2019 19:41:12 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE ListVarietyRegResolver   AWS::AppSync::Resolver Sat Jun 15 2019 19:40:53 GMT+0530 (India Standard Time)
UPDATE_COMPLETE GetVarietyRegResolver    AWS::AppSync::Resolver Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_COMPLETE UpdateVarietyRegResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:10 GMT+0530 (India Standard Time)
UPDATE_COMPLETE CreateVarietyRegResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:19 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE GetMasterRegPurposeResolver    AWS::AppSync::Resolver Sat Jun 15 2019 19:40:52 GMT+0530 (India Standard Time)
UPDATE_COMPLETE DeleteMasterRegPurposeResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:06 GMT+0530 (India Standard Time)
UPDATE_COMPLETE ListMasterRegPurposeResolver   AWS::AppSync::Resolver Sat Jun 15 2019 19:41:06 GMT+0530 (India Standard Time)
UPDATE_COMPLETE CreateMasterRegPurposeResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:12 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterPromotion-XPR1F7J9KY2V AWS::CloudFormation::Stack Sat Jun 15 2019 19:40:43 GMT+0530 (India Standard Time) User Initiated
UPDATE_IN_PROGRESS          UpdateMasterPromotionResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:46 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS          GetMasterPromotionResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:46 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS          ListMasterPromotionResolver                                                   AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:46 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS          CreateMasterPromotionResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:46 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS          DeleteMasterPromotionResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:46 GMT+0530 (India Standard Time)
UPDATE_COMPLETE             ListMasterPromotionResolver                                                   AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:03 GMT+0530 (India Standard Time)
UPDATE_COMPLETE             DeleteMasterPromotionResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:05 GMT+0530 (India Standard Time)
UPDATE_COMPLETE             GetMasterPromotionResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:20 GMT+0530 (India Standard Time)
UPDATE_COMPLETE             CreateMasterPromotionResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:21 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE DeleteVarietyNoteResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:22 GMT+0530 (India Standard Time)
UPDATE_COMPLETE ListVarietyNoteResolver   AWS::AppSync::Resolver Sat Jun 15 2019 19:41:24 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE MasterLocation AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:18 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              UpdateVarietyProfileHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:24 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateVarietyProfileHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:26 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyProfileHistory-18LNLYLX3VS2H AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:27 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetVarietyProfileResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:25 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyProfile-1WFEO2XN8N8G3 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:25 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              UpdateVarietySprResolver                                                  AWS::AppSync::Resolver
 Sat Jun 15 2019 19:41:19 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietySpr-194XT2JU1AKYC AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:19 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE GetVarietySprLineHistoryResolver    AWS::AppSync::Resolver Sat Jun 15 2019 19:41:05 GMT+0530 (India Standard Time)
UPDATE_COMPLETE CreateVarietySprLineHistoryResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:10 GMT+0530 (India Standard Time)
UPDATE_COMPLETE ListVarietySprLineHistoryResolver   AWS::AppSync::Resolver Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE ListVarietyPromLineResolver   AWS::AppSync::Resolver Sat Jun 15 2019 19:41:08 GMT+0530 (India Standard Time)
UPDATE_COMPLETE GetVarietyPromLineResolver    AWS::AppSync::Resolver Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_COMPLETE UpdateVarietyPromLineResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE ListVarietyMainResolver   AWS::AppSync::Resolver Sat Jun 15 2019 19:41:02 GMT+0530 (India Standard Time)
UPDATE_COMPLETE GetVarietyMainResolver    AWS::AppSync::Resolver Sat Jun 15 2019 19:41:05 GMT+0530 (India Standard Time)
UPDATE_COMPLETE DeleteVarietyMainResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              UpdateSpadAttachmentResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:08 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetSpadAttachmentResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:10 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateSpadAttachmentResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:19 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-SpadAttachment-1F30VIWEWC07O AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:20 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              CreateVarietyPromLineHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:03 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetVarietyPromLineHistoryResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:11 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              DeleteVarietyPromLineHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:14 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateVarietyPromLineHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:24 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyPromLineHistory-1BM5N4SMZSV74 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:25 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetMasterVarietyValueTypeResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:04 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateMasterVarietyValueTypeResolver                                               AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:06 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateMasterVarietyValueTypeResolver                                               AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:23 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterVarietyValueType-ASV7GOZCX4 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:23 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE ListVarietyAttachmentHistoryResolver   AWS::AppSync::Resolver Sat Jun 15 2019 19:41:03 GMT+0530 (India Standard Time)
UPDATE_COMPLETE CreateVarietyAttachmentHistoryResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:15 GMT+0530 (India Standard Time)
UPDATE_COMPLETE UpdateVarietyAttachmentHistoryResolver AWS::AppSync::Resolver Sat Jun 15 2019 19:41:22 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              UpdateMasterMaturityGroupResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:06 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetMasterMaturityGroupResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:08 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              ListMasterMaturityGroupResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:19 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateMasterMaturityGroupResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:24 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterMaturityGroup-1MUAXO29VIDG0 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:24 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              UpdateVarietyValueResolver                                                  AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:05 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetVarietyValueResolver                                                     AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:16 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              DeleteVarietyValueResolver                                                  AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:28 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyValue-1XCEV2LKOBSJV AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:29 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetMasterLocationResolver                                                    AWS::AppSync::Resolver
    Sat Jun 15 2019 19:41:16 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              DeleteMasterLocationResolver                                                 AWS::AppSync::Resolver
    Sat Jun 15 2019 19:41:17 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterLocation-YSWEDXC3GR7D AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:17 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              ListUserMainResolver                                                   AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:30 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-UserMain-1OTDY3NJYNI7 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:31 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetMasterParentTypeResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateMasterParentTypeResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:10 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              ListMasterParentTypeResolver                                                   AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:11 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              DeleteMasterParentTypeResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateMasterParentTypeResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:21 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterParentType-TDFB8C1K5JH0 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:21 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              ListVarietyAdaptSubResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateVarietyAdaptSubResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:11 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetVarietyAdaptSubResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:16 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyAdaptSub-1MJ5N77Q2PJ0M AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:17 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              DeleteMasterAttachTypeResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:17 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterAttachType-6V4S1KPHVB2C AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:18 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              CreateMasterTppResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:20 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterTpp-C3TLSYPL7TJ5 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:21 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetVarietyStageResolver                                                    AWS::AppSync::Resolver
  Sat Jun 15 2019 19:41:11 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              DeleteVarietyStageResolver                                                 AWS::AppSync::Resolver
  Sat Jun 15 2019 19:41:29 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyStage-ZQVFQPB3VTQ5 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:30 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              ListVarietyCompHistoryResolver                                                   AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:17 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetVarietyCompHistoryResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:27 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyCompHistory-8XXIQK21TUU9 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:28 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetVarietyCompResolver                                                    AWS::AppSync::Resolver
 Sat Jun 15 2019 19:41:19 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyComp-4QSSE80W5G9G AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:20 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              CreateMasterReportResolver                                                  AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetMasterReportResolver                                                     AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:19 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              ListMasterReportResolver                                                    AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:24 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterReport-1KMM7974C4FWI AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:25 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyNote-7M3L6HT5JFZG AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:25 GMT+0530 (India Standard Time)

UPDATE_COMPLETE                              UpdateMasterPromotionResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:29 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterPromotion-XPR1F7J9KY2V AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:31 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetMasterCompPromResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:31 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterCompProm-198QA3U4AUO8G AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:32 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

 This may take a few minutes...

UPDATE_COMPLETE                              UpdateMasterRegPurposeResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:25 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterRegPurpose-1XYPEU556F0OM AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:26 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              DeleteVarietySprLineResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:11 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetVarietySprLineResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:16 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietySprLine-1TRA2OI146AA1 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:17 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              ListMasterZoneResolver                                                    AWS::AppSync::Resolver
 Sat Jun 15 2019 19:41:00 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateMasterZoneResolver                                                  AWS::AppSync::Resolver
 Sat Jun 15 2019 19:41:00 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateMasterZoneResolver                                                  AWS::AppSync::Resolver
 Sat Jun 15 2019 19:41:03 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              DeleteMasterZoneResolver                                                  AWS::AppSync::Resolver
 Sat Jun 15 2019 19:41:15 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterZone-1S1V2TV10Y3UH AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:16 GMT+0530 (India Standard Time)

UPDATE_COMPLETE                              DeleteMasterTraitResolver                                                  AWS::AppSync::Resolver
  Sat Jun 15 2019 19:41:25 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterTrait-1UXJY1VY29N0T AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:26 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              DeleteVarietyRegResolver                                                 AWS::AppSync::Resolver
Sat Jun 15 2019 19:41:43 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyReg-EO47IHC2Y3TQ AWS::CloudFormation::Stack
Sat Jun 15 2019 19:41:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE VarietyAttachmentHistory AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:44 GMT+0530 (India Standard Time)
UPDATE_COMPLETE VarietySprLineHistory    AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:44 GMT+0530 (India Standard Time)
UPDATE_COMPLETE UserMain                 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:44 GMT+0530 (India Standard Time)
UPDATE_COMPLETE VarietyReg               AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:45 GMT+0530 (India Standard Time)
UPDATE_COMPLETE VarietyPromLine          AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:45 GMT+0530 (India Standard Time)
UPDATE_COMPLETE MasterCompProm           AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:46 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              DeleteVarietySprLineHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:30 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateVarietySprLineHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:39 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietySprLineHistory-1SR74JQSOASZU AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:40 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              DeleteVarietyPromLineResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:34 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyPromLine-1RWYNPUUVDHD5 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:34 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              CreateVarietyMainResolver                                                  AWS::AppSync::Resolver
  Sat Jun 15 2019 19:41:38 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateVarietyMainResolver                                                  AWS::AppSync::Resolver
  Sat Jun 15 2019 19:41:47 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyMain-1HM3KZKJWOJWL AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:48 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              DeleteVarietyAttachmentHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:40 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyAttachmentHistory-1EVVILBK9IY5D AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:41 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE VarietyMain AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:01 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              CreateVarietyTppAdaptResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:14 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyTppAdapt-A01WD6YWIFTV AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:14 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS SearchableStack AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:03 GMT+0530 (India Standard Time)
UPDATE_COMPLETE    ConnectionStack AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:03 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetMasterMarketSegmentResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:14 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterMarketSegment-1558YHMOK8CCN AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:15 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-SearchableStack-IZWY4C23TY9T AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:13 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              SearchableStack                                  AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:15 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:17 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE apispadApp AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:24 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:25 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS                           apispadApp              AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:26 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_IN_PROGRESS SearchableStack AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:28 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS ConnectionStack AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:28 GMT+0530 (India Standard Time)
UPDATE_COMPLETE    ConnectionStack AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:29 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetVarietyRegResultResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:12 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyRegResult-KXYQ5P3IBSA2 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-SearchableStack-IZWY4C23TY9T AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:30 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE    SearchableStack  AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:39 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS MasterParentType AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:42 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

 This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyAdaptSub-1MJ5N77Q2PJ0M AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

 This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterTpp-C3TLSYPL7TJ5 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterReport-1KMM7974C4FWI AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterRegPurpose-1XYPEU556F0OM AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyProfileHistory-18LNLYLX3VS2H AWS::CloudFormation::Stack Sat Jun
15 2019 19:42:45 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyCompHistory-8XXIQK21TUU9 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyPromLine-1RWYNPUUVDHD5 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyRegResult-KXYQ5P3IBSA2 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetMasterMaintenanceResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:10 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterMaintenance-1WENEGWNHX6RW AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:11 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterMaintenance-1WENEGWNHX6RW AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyValue-1XCEV2LKOBSJV AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              CreateMasterNoteTypeResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:57 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetMasterNoteTypeResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:57 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              ListMasterNoteTypeResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:59 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateMasterNoteTypeResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:05 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              DeleteMasterNoteTypeResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:15 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterNoteType-10VCLN5VEV05J AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:15 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterNoteType-10VCLN5VEV05J AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterCompProm-198QA3U4AUO8G AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              ListVarietyTppAdaptHistoryResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:03 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateVarietyTppAdaptHistoryResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:04 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetVarietyTppAdaptHistoryResolver                                                     AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:12 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyTppAdaptHistory-1XJYOD6PX0EEA AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyTppAdaptHistory-1XJYOD6PX0EEA AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetParentCharacteristicsResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:05 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateParentCharacteristicsResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:07 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-ParentCharacteristics-QN6GOJUOL52D AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:08 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-ParentCharacteristics-QN6GOJUOL52D AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyAttachmentHistory-1EVVILBK9IY5D AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyReg-EO47IHC2Y3TQ AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterVarietyValueType-ASV7GOZCX4 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyAttachment-15T4VI9NPPCWF AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              ListVarietyPromotionHistoryResolver                                                   AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:00 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateVarietyPromotionHistoryResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateVarietyPromotionHistoryResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              DeleteVarietyPromotionHistoryResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:15 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetVarietyPromotionHistoryResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:16 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyPromotionHistory-KMQVMTYAQTC7 AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:17 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyPromotionHistory-KMQVMTYAQTC7 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyComp-4QSSE80W5G9G AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyProfile-1WFEO2XN8N8G3 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterTechSegment-KY15YUVDPA24 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyPromLineHistory-1BM5N4SMZSV74 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterPromotion-XPR1F7J9KY2V AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              ListVarietyNoteHistoryResolver                                                   AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:08 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateVarietyNoteHistoryResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyNoteHistory-OJ4R4BPOKI0H AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:10 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyNoteHistory-OJ4R4BPOKI0H AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterAdpZone-1GZXZR6CE1939 AWS::CloudFormation::Stack Sat Jun 15 2019
19:42:44 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE          apispadApp              AWS::CloudFormation::Stack Sat Jun 15 2019 19:43:01 GMT+0530 (India Standard Time)
UPDATE_IN_PROGRESS       authcognito5435110d     AWS::CloudFormation::Stack Sat Jun 15 2019 19:43:02 GMT+0530 (India Standard Time)
UPDATE_COMPLETE          authcognito5435110d     AWS::CloudFormation::Stack Sat Jun 15 2019 19:43:03 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745 AWS::CloudFormation::Stack Sat Jun 15 2019 19:43:03 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-varietySprHistory-18O7KG7ZU6915 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterLocation-YSWEDXC3GR7D AWS::CloudFormation::Stack Sat Jun 15 2019
19:42:44 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietySpr-194XT2JU1AKYC AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:43 GMT+0530 (India Standard Time)

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-UserMain-1OTDY3NJYNI7 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterAttachType-6V4S1KPHVB2C AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyStage-ZQVFQPB3VTQ5 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterTrait-1UXJY1VY29N0T AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              GetMasterGradingResolver                                                    AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:00 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              DeleteMasterGradingResolver                                                 AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:06 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              ListMasterGradingResolver                                                   AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:09 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateMasterGradingResolver                                                 AWS::AppSync::Resolver
   Sat Jun 15 2019 19:41:11 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterGrading-JGGCUN0RP7SM AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:12 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterGrading-JGGCUN0RP7SM AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterMarketSegment-1558YHMOK8CCN AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyTppAdapt-A01WD6YWIFTV AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterStage-1QEH3WYSKUS4R AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-SpadAttachment-1F30VIWEWC07O AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              UpdateMasterCategoryResolver                                                 AWS::AppSync::Resolver
    Sat Jun 15 2019 19:41:02 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              ListMasterCategoryResolver                                                   AWS::AppSync::Resolver
    Sat Jun 15 2019 19:41:04 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateMasterCategoryResolver                                                 AWS::AppSync::Resolver
    Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterCategory-5PDDMDVTREBD AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:14 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterCategory-5PDDMDVTREBD AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:43 GMT+0530 (India Standard Time)

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyPromotion-1IHJZJZWPX69G AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterZone-1S1V2TV10Y3UH AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:43 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietySprLineHistory-1SR74JQSOASZU AWS::CloudFormation::Stack Sat Jun
15 2019 19:42:43 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyMain-1HM3KZKJWOJWL AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:43 GMT+0530 (India Standard Time)
- Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              CreateVarietyStageHistoryResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:57 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              ListVarietyStageHistoryResolver                                                   AWS::AppSync::Resolver     Sat Jun 15 2019 19:40:59 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateVarietyStageHistoryResolver                                                 AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:11 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              GetVarietyStageHistoryResolver                                                    AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:12 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyStageHistory-R1LU6OD8767G AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyStageHistory-R1LU6OD8767G AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterMaturityGroup-1MUAXO29VIDG0 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:43 GMT+0530 (India Standard Time)
| Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietyNote-7M3L6HT5JFZG AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:43 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-VarietySprLine-1TRA2OI146AA1 AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
\ Updating resources in the cloud. This may take a few minutes...

UPDATE_COMPLETE                              DeleteMasterRegStatusResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:04 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              CreateMasterRegStatusResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
UPDATE_COMPLETE                              UpdateMasterRegStatusResolver                                                  AWS::AppSync::Resolver     Sat Jun 15 2019 19:41:13 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterRegStatus-17NBZK983BAYU AWS::CloudFormation::Stack Sat Jun 15 2019 19:41:14 GMT+0530 (India Standard Time)
UPDATE_ROLLBACK_COMPLETE                     spad-app-20190517170745-apispadApp-1PZDC8K4RJDFM-MasterRegStatus-17NBZK983BAYU AWS::CloudFormation::Stack Sat Jun 15 2019 19:42:44 GMT+0530 (India Standard Time)
/ Updating resources in the cloud. This may take a few minutes...

 This may take a few minutes...Error updating cloudformation stack
/ Updating resources in the cloud. This may take a few minutes...

Following resources failed

× An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete

This really needs a solution or better documentation on how to manually work around these types of issues.
I've hit this now twice in a few days and it got me stuck for hours.  It takes 10-25 minutes for every attempt you make to do fail and then the rollback.
If it's not simple to solve this in an automated way, then the CLI should either warn (for example when compiling the schema, it could warn and wait for confirmation if a named connection is changed, it's a simple line diff?). And if it fails, more debug information could be provided to know where to go and try a manual fix.
The platform I am working on is not live yet (it will be in a week) and I dread that this will happen once it's live, without really knowing what to do and not having the option to delete. Doing amplify delete api is not that simple anymore as I believe it will stop when it detects that other resources depend on it (which is a good thing) and once you re-create it the dynamic name is changed, which may affect code in the project.

@houmark we are investigating ways to solve this in an orchestrated manner, as noted earlier this is due to a way that DynamoDB manages GSIs. However your suggestion of "warning" is an area we've decided to look into in the short term and had a couple of design sessions on it last week. @kaustavghosh06 and @mikeparisstuff are looking at the best way to inform you if you're making a change that might cause this issue while we look further into a longer term implementation that could handle this automatically behind the scenes.

@undefobj thanks for your feedback on this. It's nice to know that it's on your radar. Having now worked on a platform for a few weeks in Amplify, this has been my single most concerning experience, and something that makes me doubt if this is a platform I want to commit to. For this project, I am too far in, and I have to stick around, but it really worries me that cloud resources can get to such a corrupted state, by simply changing a field name or tweaking a connection name. At this point, I am not even sure what was the original reason for all my problems.
This is really really bad. I now spent the entire day trying everything and the one thing that I don't get is the resolvers, where they are to start with, in order to change/tweak them.
Even though I am in dev mode and even though I had already pushed a simple schema that deleted my entire dev database, I was still not able to get back to a normal functioning state. So I gave up and decided to delete the entire api, which was a long process in itself, as I had to remove dependencies for all other resources to the api. Since I have a @searchable on one type, the creation is slow. But I should never have to get to here.
So my suggestion is:

Short term: You come up with some kind of improved parser that already before the push will warn and be fairly detailed in the warning, so the developer can reconsider this or manually do changes in the cloud before doing the push, in order to prevent things from going into this state where you feel like you completely lost control

Long term: Fix the cloud, so it's more intelligent about these changes. It seems to me that some race situations are happening and maybe some resolvers are not correctly removed, leaving them hanging around and preventing new ones from being attached.

There's no way in my knowledge to list all resolvers, so even though the terminal is telling me that xyzrsolvername is giving problems, I am yet to find a way to go to the UI, find the resolver and delete it. I tried to manually add the field back on the schema, but it did not show up.
I understand that this is complicated and a fully automated solution may be very hard to accomplish, so while I'm sure that is eventually possible, better client-side "validations" and warnings and better documentation on how to manually attempt resolving this is what one could expect on a platform Amazon believes is ready for production projects.

So the last official update on this was on the 21. May? It is now the 5. July and this is still completely broken? If you ever try to push a wrongly named field or connection your entire API is f**ked and there is no way of fixing it?

Hey guys, we've been actively looking into this issue and will have a short term solution out for it in 1-2 weeks. As @houmark mentioned in his "Short term" solution section, we'll be adding a sanity check parser to check if any changes to your schema (basically a diff between whatever is deployed to the cloud and the changes in your local schema) would cause a cloudformation push error and fail fast - before the cloudformation  push. This check would clearly mention why the sanity check failed and what should be your path forward from there.
Here are the cases we've identified for the sanity check so far:

You cannot change an existing GSI for a DynamoDB Table
You cannot add and remove a GSI on a DynamoDB table at the same time
Protect against the duplicate resolvers

Please let us know if we've missed any other use-cases/scenarios.

Add to list:

You cannot add more than one GSI at a time (at least that seems to have been what I was fighting with a lot)

@houmark Updated my comment. Thank you.

Update: We are adding tooling that will fail prior to the push when you try to push a migration that is known to fail. E.G. changing a GSI, adding and removing a GSI at the same time, changing a key schema, adding LSIs after table creation, etc. We are also adding a suite of tests that cover these migration scenarios that will prevent these issues moving forward. You may track the progress here if interested https://github.com/aws-amplify/amplify-cli/pull/1815.

Doesn't this also mean that any table with >1 GSI keeps you from being able to create a new environment with multienv?

Doesn't this also mean that any table with >1 GSI keeps you from being able to create a new environment with multienv?

This only happens when updating a resource. When you create a new environment, it creates new resources for those.

Hi everyone, wanted to update on this issue. We got the sanity check/validations working as mentioned out here - https://github.com/aws-amplify/amplify-cli/issues/922#issuecomment-509418653  and we merged the PR for it (#1815). We'll be publishing a new version of the CLI (1.8.6) early next week with this change.

Hey guys, we published the sanity check feature out. This would basically prevent pushing of invalid schema changes by giving a reason and provide a way to go around the change.

I'm still seeing the error message. Cannot perform more than one GSI creation or deletion in a single update; Is this fixed?

I think this should only prevent it from ever happening. If it's happened, then I think there's still no solution.

this issue just got me with out any prior warning when pushing updates to the schema...fortunately dev. Amplify v.4.16.1

Same, just got this issue. Added a few @key's to a couple of different models and tried to push to my dev environment, got this:
UPDATE_FAILED      InformationEntryTable                      AWS::DynamoDB::Table   Mon May 11 2020 12:29:34 GMT+0100 (British Summer Time) Cannot perform more than one GSI creation or deletion in a single update

Amplify 4.18.1

My issue is, if I understand that I can only make one change using @key or @connection per update, that's fine. but then I push my feature into a production branch for feature deploy. then my amplify CI is going to try more than one change and it'll get this error.
I think this is unworkable in it's present state!

This is still failing. It failed when changing my table columns names to camelCase. This should not be closed.

Is there any news on this issue ? Still having to recreate the whole schema each time you do a simple edit around @connection link between two entities in the graphQL schema.

Why on gods' earth is this issue closed. Issue is still present. Amplify is turning into a complete disaster. Y'all should completely restart from scratch with a different name to distance yourself from the unfixable mess this dis-service has become.

Isn't the solution to this to this is if it happens to a table...then delete them all and then add them back one at a time...doesn't seem complicated to me...it would be nice if there was an amplify push --resetGSI that did this automatically...

Isn't the solution to this to this is if it happens to a table...then delete them all and then add them back one at a time...doesn't seem complicated to me...it would be nice if there was an amplify push --resetGSI that did this automatically...

That would lead to downtime on production where no data can be returned because it's depending on the index, while the indexes are backfilling, and for large setups backfilling can take some time, especially if you have many indexes on that table.
I am still hitting situations where the tooling does not detect the multiple GSI error before starting the push, leading to a rollback and it can be really hard to estimate how many GSI changes a fairly simple change results. In addition, it's normal to make multiple changes in dev and then push all that to production, which then results in the same error on production.
I don't understand why the CLI can do several passes on GSI's by detecting the amount needed to be done, do one, wait for it to finish, do another and so on... then finish the entire push.

@houmark FWIW: I agree with you I think the tooling should handle this. When I've hit this I edit the graphql and step the change through manually. There is no reason that could not be automated. To that end I've submitted this: https://github.com/aws-amplify/amplify-cli/issues/4885
Please add expand on this.

+1

Hey guys, we published the sanity check feature out. This would basically prevent pushing of invalid schema changes by giving a reason and provide a way to go around the change.

I'm on the latest version and I just got the rollback error... again.

+1. Need a alternative way as well since I cannot remove my api

+1. Need a alternative way as well since I cannot remove my api


Handle formData parameters in Case.call

Codecov Report

Merging #224 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #224      +/-   ##
==========================================
+ Coverage   99.89%   99.89%   +<.01%
==========================================
  Files          19       19
  Lines         983      986       +3
  Branches      147      148       +1
==========================================
+ Hits          982      985       +3
  Partials        1        1

Flag
Coverage Δ

#unittests
99.89% <100%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

src/schemathesis/models.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ef186f3...52812c3. Read the comment docs.


Compilation of missing Attr operations succeeds while it should not

@kustosz commented on Mon Jun 18 2018
consider this code:
type instance Pass.Spec DesugarListLiterals t = DesugarListLiteralsSpec t
type family DesugarListLiteralsSpec t where
    DesugarListLiteralsSpec (Pass.In  Pass.Attrs) = '[Root, UniqueNameGen]
    DesugarListLiteralsSpec (Pass.Out Pass.Attrs) = '[UniqueNameGen]
    DesugarListLiteralsSpec t = Pass.BasicPassSpec t

instance ( Pass.Interface DesugarListLiterals (Pass.Pass stage DesugarListLiterals)
         , IR.DeleteSubtree (Pass.Pass stage DesugarListLiterals)
         ) => Pass.Definition stage DesugarListLiterals where
    definition = do
        Root root <- Attr.get
        Attr.put $ Root root

This compiles, even though Root is not a writable attribute inside this pass.

I'm lowering its priority. It's definitely not critical. It's nice to have all these type-level checks but without them, nothing breaks currently.


Upgrade CaaSP nodes after velum registration

Yeah, velum seems to work well. I'm just not yet sure if it will end with stable cluster

Do we still need this?

Nope


Added CK Token to Defaults

website: https://cryptokitties.co
chat: https://discord.gg/3GvT66U
reddit: https://www.reddit.com/r/CryptoKitties/

Actually... this is the wrong place, CK is ERC-721, not ERC-20 :sad trombone:

Actually, let's leave it open so we secure CK namespace. ERC-721 methods are mostly compatible with ERC-20


Fix Maze::positionConsideringTunnel()

This fixes the Demo crashing at tunnels: #90
The Maze::positionConsideringTunnel() now always returns a valid maze position, by either wrapping or clamping (tunnel or wall).
#patch

@ll-nick :)


Syncplay now crashes when passing player arguments that worked fine before

It is common for my friends to keep the following in their player arguments field: --ytdl-format=bestvideo[height<=1080] in order to reduce bandwidth by not streaming youtube videos and the like in 4K.  With the latest syncplay, these player arguments started causing immediate crashes of syncplay/mpv, even before any media attempts to load.
Specifically, we tested this on windows, using mpv.exe as the player.
I narrowed down the issue to the = character.  Specifically, I can use --ytdl-format=bestvideo[height<1081] as a workaround.  I hope this helps diagnose the bug.

I have this problem too, removing the = sign from commands lets syncplay start normally.
Before version 1.6.4a i did not have the problem.

Thanks for reporting this issue. Is it resolved by f7ca631e08564db92508b183fa81622c4df16fcd?


Ordered and unorederd lists are too spaced - how to make them more compact?

As the title says, they are very much too spaced (as you can even see in the example screenshots), and I can't for the life of me, not with rules and not with styles figure out how to fix it.
Can this even be achieved? Thanks!

Have you tried using the debugPrintTree to see which rules you need to change?

take a look at 7.0.0-alpha - i think that might have the changes you want to the styles built in

I didn't realise there was a new alpha. Just upgraded and it fixes things, thanks!
Also, thank you for all of your work on this, it's great! :)


Improving Modularity, Error Handling, and Code Readability

Description
The current implementation of the personal assistant script could benefit from improvements in terms of modularity, error handling, and overall readability. The core functionality works well, but refactoring the code into smaller, more manageable components would make it easier to maintain and expand. Additionally, speech recognition logic can be centralized for consistency.
Proposed Enhancements
1. Refactoring to Modular Functions:
Moving specific tasks such as handling time, weather, Wikipedia searches, and application opening into their own functions.
This will reduce redundancy and improve readability by keeping the main loop clean.
2. Introducing recognize_speech_with_timeout() Function
Creating a dedicated recognize_speech_with_timeout() function to:

Handle speech recognition uniformly throughout the script.
Include consistent handling for timeouts and exceptions.
Avoid repetition of speech recognition code in multiple places.

3. Improve Error Handling
Adding more specific exception handling in individual feature functions.
Providing clearer, more user-friendly feedback when errors occur (e.g., speech recognition timeouts or issues fetching data).
Benefits
Increased Code Readability: By modularizing the code, future contributors can easily find and modify specific sections.
Improved Maintainability: Centralized error handling and speech recognition will make it easier to update and debug.
Better User Experience: Users will receive more informative feedback when something goes wrong (e.g., speech recognition fails or times out).

@suryanshsk  , as a participant in Girls Script Summer of Code ext (GSSOC ext), I'd like to work on this issue. Could you please assign it to me and add the GSSOC ext label.


Is there any open source code for this paper in medical?

Hey Guang, Bo and Tongzhou,
Thank you for maintaining this great repository!
The paper in application of medical Soft-Label Anonymous Gastric X-ray Image Distillation (Guang Li et al., ICIP 2020)] has been marked a "code" icon.
However when I click on the icon, the page does not jump correctly, and it also jumps to the current repository.
Does this paper have open source code? I didn't find any relevant content on github. If you can provide relevant ideas, I would be very grateful!
Thanks for the consideration.

Hey Erica,
First of all, thank you for your interest in my paper, because the research involves a private dataset from the University of Tokyo and hence we have not made the code publicly available, but our research is based on the soft-label dataset distillation and implemented according to its repo, which you can check it at here. I apologize for the code tag because this paper collection project begins with this paper, so I added the code tag, which has been fixed.
Best,
Guang

Hey Guang,
Thank you for your prompt reply and your efforts to organize the paper.
I'll look into the link you shared, thanks again!
Best,
Erica


to add open source flutter apps

flutter-chat-demo
(https://github.com/duytq94/flutter-chat-demo)
A chat app made by Flutter and Firebase that supports login with google account, chat with any user, send text, image and sticker, update avatar and profile.

@ashitaprasad please assign me this issue under gssoc'24


select onMouseDown added

[x] I have followed (at least) the PR section of the contributing guide.
i changed onclick to onMouseDown ,is this correct?
#8999

Humm, this one will be challenging to implement.


Revamp mp4 video handling

The primary focus of this PR is abstracting mp4 video into VideoLoopView. Downloaded mp4s are now put into the PINCache via VideoCache which required a slight tweak to PINCache's file path encoding.

Executed 2568 tests, with 0 failures (0 unexpected) in 195.867 (196.754) seconds


Cannot mute failed checks based on AWS tags using 4.3.0

Steps to Reproduce

Create tagged AWS resources (tested with EC2 instances, IAM roles)
Add tag-based mute list entry matching those resources
Run prowler with the mutelist

Expected behavior
Findings related to the muted checks are reported as muted for the tagged resources.
Actual Result with Screenshots or Logs
Related findings are not muted, causing prowler to exit with a non-zero exit code. Additionally, no findings are muted for checks in the mutelist containing both specific resources as well as tags. Meaning not only do tag-based mutelist entries not work, they seem to break the entire mutelist entry for the relevant check.
Note: When the mutelist contains an empty array of tags for a check, the resource-based exclusions still work. Adding an empty string value also has no negative impact. But even adding one of the examples (environment=dev) breaks the resource-based muting.
How did you install Prowler?
From pip package (pip install prowler)
Environment Resource
Workstation/GitHub Actions
OS used
ubuntu-latest (GitHub Actions)/Fedora 40 Workstation
Prowler version
4.3.0
Pip version
24.2
Context
No warnings/errors are logged regarding our mutelist. When reverting back to 4.2.4, all findings are muted as expected using the exact same mutelist.
I could not find any obvious (to me) reason for the tags breaking while quickly looking through the mutelist code. My best guess is that this issue was somehow introduced by #4413 (just looking for changes to the mutelist added with 4.3.0).

I was able to reproduce this with a super simple mutelist:
Mutelist:
  Accounts:
    '*':
        ec2_instance_detailed_monitoring_enabled:
          Regions: ['*']
          Resources: ['*']
          Tags:
            - 'Name=Database/AdminInstance'

I just noticed that the tags "breaking" resource-based entries might be a misunderstanding on my part. Just to clarify: Are the different mutelist options applied as AND or as OR? If it's AND then of course the failed checks in the under Resources don't get muted if those resources don't also have the relevant tag.

One more (potentially) important piece of information: I do see the exact tag from the mutelist in the RESOURCE_TAGS column of the findings, so it both exists and is detected by prowler (along with all the other tags on that instance).

Thanks for the information @cetteup !
We have identified the issue and working now on a fix.
About your question, the mutelist acts as an OR.

For me this appears to work as long as the tags do not contain a forward slash /.
This works:
Mutelist:
  Accounts:
    "*":
      Checks:
        "some_check_name":
          Regions: ["*"]
          Resources: ["*"]
          Tags:
            - "aws:eks:cluster-name=dev"

But this doesn't:
Mutelist:
  Accounts:
    "*":
      Checks:
        "some_check_name":
          Regions: ["*"]
          Resources: ["*"]
          Tags:
            - "'karpenter.sh/managed-by'=dev"

I quickly retested this with some simpler tags (and a working mutelist, the above example was missing the Checks key, which did not raise any errors but also did nothing). As soon as I add any tag, the check is not muted anymore - even if I specifically mention the affected resource under Resources. Happens for me even with tags as simple as thekey=thevalue.
Mutelist:
  Accounts:
    '*':
      Checks:
        ec2_instance_detailed_monitoring_enabled:
          Regions: ['*']
          Resources: ['*']
          Tags:
            - 'thekey=thevalue'

When I grep through the output CSV with the same tag, I get a match.

I quickly retested this with some simpler tags (and a working mutelist, the above example was missing the Checks key, which did not raise any errors but also did nothing). As soon as I add any tag, the check is not muted anymore - even if I specifically mention the affected resource under Resources. Happens for me even with tags as simple as thekey=thevalue.
Mutelist:
  Accounts:
    '*':
      Checks:
        ec2_instance_detailed_monitoring_enabled:
          Regions: ['*']
          Resources: ['*']
          Tags:
            - 'thekey=thevalue'

When I grep through the output CSV with the same tag, I get a match.

Hello @cetteup, this is strange because the above Mutelist works in our test environments 🤔
Could you be able to jump into a quick call to review it? You can join our Prowler Slack using this invite link https://join.slack.com/t/prowler-workspace/shared_invite/zt-2luugg3ld-_MlE692tRwAZoMMrZ1sV7w

@thomscode could you share with us the Mutelist you are using and the tags present in your resource because we are not being able to reproduce this issue.

After a brief chat with @jfagoagas, I set up a fresh EC2 instance and started gradually adding tags. With an interesting finding: Muting works with whatever tag is shown first in the tag list of the AWS web console. Meaning it works by default with a single tag, but stops working as soon as you have more than one tag and are not using the first one. Also verified with our existing EC2 instances. Tag we actually want to use is 7th in the list. If I use the first listed tag instead, muting works.

That's exactly what I saw in some tests I did 🤔 Let me add some unit tests and see ...

@cetteup @thomscode could you please run Prowler again with the code in the above PR? The branch name is PRWLR-4383-cannot-mute-failed-checks-based-on-aws-tags-using-4-3-0-fix.
Thanks in advance!

Version on the branch works with non-first tags, including ones with special characters (e.g. the initial Name=Database/AdminInstance). Nice work! 🚀
Only "issue" that remains (which may not be unrelated/a misunderstanding): When I try to mute both a specific resource by and another one by a tag for the same check, findings for neither end up being muted. If Resources and Tags are really OR-linked, I believe I should be able to do something like
Mutelist:
  Accounts:
    '*':
      Checks:
        ec2_instance_detailed_monitoring_enabled:
          Regions: ['*']
          Resources:
            - 'i-123456789' # Mute specific resource by name
          Tags:
            - 'Name=Database/AdminInstance' # AND mute other resource by tag

Thank you for testing it!!
Regarding the mutelist logic, as far as I know, at least is coded in that way, the fields are AND-linked, e.g.:
With the following Mutelist:
Mutelist:
  Accounts:
    '*':
      Checks:
        ec2_instance_detailed_monitoring_enabled:
          Regions: ['*']
          Resources:
            - 'i-123456789' # Mute specific resource by name
          Tags:
            - 'Name=Database/AdminInstance' # AND mute other resource by tag

Resource: i-123456789 without tags -> NOT MUTED
Resource: i-123456789 with tag 'Name=Database/AdminInstance' -> MUTED
Resource: i-00000000 with tag 'Name=Database/AdminInstance' -> NOT MUTED

Thanks for clarifying and documenting it. Issue is good to be closed now when merging the PR.
Is there any other way of achieving the above-described kind of OR-ed muting? We have some CDK-created resources which are simply called default but have more specific tags. However, we need to mute the same check for resources without any usable tags (but distinct names).

Hello @thomscode, could you please share with me some examples to help you craft a valid Mutelist for your use case?
Something like the following:

Account/s
Check/s
Resource/s and their tag/s

@jfagoagas,
Below is what is working now. As Karpenter adds and removes nodes I'm having to add new tags each instance will have a different first tag.
Mutelist:
  Accounts:
    "....":
      Checks:
        "ec2_instance_secrets_user_data":
          Regions:
            - "us-west-2"
          Resources:
            - "*"
          Tags:
            - "karpenter.sh/managed-by=dev"
            - "aws:eks:cluster-name=dev"
            - "karpenter.sh/nodepool=default"
            - "karpenter.sh/nodepool=medium"
            - "karpenter.sh/nodepool=4xlarge"
            - "karpenter.k8s.aws/ec2nodeclass=default"
            - "karpenter.k8s.aws/ec2nodeclass=medium"
            - "karpenter.k8s.aws/ec2nodeclass=4xlarge"
            - "kubernetes.io/cluster/dev=owned"

@jfagoagas,
Below is what is working now. As Karpenter adds and removes nodes I'm having to add new tags each instance will have a different first tag.
Mutelist:
  Accounts:
    "....":
      Checks:
        "ec2_instance_secrets_user_data":
          Regions:
            - "us-west-2"
          Resources:
            - "*"
          Tags:
            - "karpenter.sh/managed-by=dev"
            - "aws:eks:cluster-name=dev"
            - "karpenter.sh/nodepool=default"
            - "karpenter.sh/nodepool=medium"
            - "karpenter.sh/nodepool=4xlarge"
            - "karpenter.k8s.aws/ec2nodeclass=default"
            - "karpenter.k8s.aws/ec2nodeclass=medium"
            - "karpenter.k8s.aws/ec2nodeclass=4xlarge"
            - "kubernetes.io/cluster/dev=owned"

I don't get the point of the concept first tag because it doesn't matter to Prowler their position. So if you have several resources with different tags, as the tags works as an OR that should work fine, it is the way to go for your use case.

@jfagoagas,
When I first experienced a problem with Prowler not respecting my tags in the mute list, I thought it had to do with the / in my tag. But after @cetteup mentioned that Prowler was only muting for the first tag in the list of tags on the AWS web console, I verified that the tag that worked was the first one listed for my instance in the AWS CLI.
All of the tags mentioned above are on all of my EC2s managed by Karpenter. But they are not all added in the same order. In Prowler 4.3.1, I am required to add multiple tags to the list because any one of them will not catch all of the EC2s even though the tag exists on all of the EC2s.
Using the code merged by the PR that resolves this issue, any of the above tags will work and only 1 is necessary.
I’m sorry for any confusion, this is just my experience.
If you want to replicate the problem try the following:

Create 2 EC2s
Add the same 2 tags to both, but in opposite order (the second tag on the first EC2 is the first tag on the second EC2)
Create a mute list with only one of the tags listed
Scan your EC2s for problems with Prowler 4.3.0 or 4.3.1

You should find that only one of your EC2s passes the scan (assuming the EC2s have a vulnerable setting).

That's totally fine, it was just a lack of context, thank you very much for all the details 👏

Hello @cetteup , could you please share with me some examples to help you craft a valid Mutelist for your use case?
Something like the following:

Account/s
Check/s
Resource/s and their tag/s

Sorry for the late reply @jfagoagas.
We ended up just having to use the default name used by CDK for the mutelist, since it was an IAM inline policy - which ofc does not have any tags (only the role itself does). I originally wanted to avoid having to add something as generic as default to the mutelist, but there was no way around it. For this scenario, tags don't matter. Though it would be nice to be able to mute findings by resource id, since that is more specific than muting any resource called default.
The idea regarding ORing resources and tags based on the following scenario: Given an account with two IAM roles. Role OrgRole is managed by the organisation admins and has no tags (which we cannot change, as it's managed by them). Role LocalRole is managed by my team, so we can add whatever tags we like. The OrgRole forces us to mute IAM roles by name, as it does not have any tags. That's fine given just our LocalRole, which is just one additional entry. But as soon as we start adding a bunch more local roles we need to mute the check for, our mutelist grows accordingly.
Having an option to mute OrgRole by name but still being able to mute manageable roles via tags would be great for this kind of scenario. Though, admittedly, I don't know how common this is.

Hello @cetteup , could you please share with me some examples to help you craft a valid Mutelist for your use case?
Something like the following:

Account/s
Check/s
Resource/s and their tag/s

Sorry for the late reply @jfagoagas.
We ended up just having to use the default name used by CDK for the mutelist, since it was an IAM inline policy - which ofc does not have any tags (only the role itself does). I originally wanted to avoid having to add something as generic as default to the mutelist, but there was no way around it. For this scenario, tags don't matter. Though it would be nice to be able to mute findings by resource id, since that is more specific than muting any resource called default.
The idea regarding ORing resources and tags based on the following scenario: Given an account with two IAM roles. Role OrgRole is managed by the organisation admins and has no tags (which we cannot change, as it's managed by them). Role LocalRole is managed by my team, so we can add whatever tags we like. The OrgRole forces us to mute IAM roles by name, as it does not have any tags. That's fine given just our LocalRole, which is just one additional entry. But as soon as we start adding a bunch more local roles we need to mute the check for, our mutelist grows accordingly.
Having an option to mute OrgRole by name but still being able to mute manageable roles via tags would be great for this kind of scenario. Though, admittedly, I don't know how common this is.

It's totally fine, now it is me who is late since I was OOO.
I get your use case and we'll try to give it a thought to see if something can be made to improve it but I think is something not too common.
Regarding a way to use the resource UUID instead of the name is something that is in our roadmap to start thinking about it and see if it worths the change.