You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Active condition for each resource is created and updated to true when the resource is created. Additionally, it is updated to false in the case where a describe call returns "Deleted" or "Inactive". However, in the case where the Mesh custom resource is deleted, which in turn deletes all resources in the mesh from the App Mesh API, we do not mark the statuses to false because the resource processing quits early due to this check in virtual node (a similar one exists in virtual service):
The Active condition for each resource is created and updated to true when the resource is created. Additionally, it is updated to false in the case where a describe call returns "Deleted" or "Inactive". However, in the case where the Mesh custom resource is deleted, which in turn deletes all resources in the mesh from the App Mesh API, we do not mark the statuses to false because the resource processing quits early due to this check in virtual node (a similar one exists in virtual service):
There are probably more cases where we should.
The text was updated successfully, but these errors were encountered: