)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"5cd8bfe6e40d7db5bd7a1ab2987f6a8ea7b1b60c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"023c5a34_b0ad4576","updated":"2022-07-05 15:37:49.000000000","message":"recheck\n\ntimeout during downloading package data","commit_id":"8ca1e5200c9d528c239ccd8cdcc024b0f8560dc4"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"c679921bfb0973c6f65605017c96c47eb625b9dd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"6f9523ab_9c53d93f","updated":"2022-07-06 04:09:27.000000000","message":"Giving it another thought, we might want to keep RemovalPolicies to exclude specific indexes, otherwise if there is a deployment with id 1 removed then there is not good way to keep that during upgrade, unless we have this.\n\nThis also makes me notice that we also need to extract RemovalPolicies from existing stack (instead of template) during upgrade .","commit_id":"0cd16d79386d167c2cb60490977cd14fcdd89202"}]}