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
I'm wondering what in the code guarantees that I'm not deleting a changeset before the related deployment from the aws CLI on a separate process manages to read the result of the creation of that changeset.
From reading the code, unless I'm mistaken, it seems that it may instantly delete any changeset that was just created, possibly not letting the time to whoever created it to collect its status first.
This means it may cause concurrent deployments to fail.
Am I mistaken, or is that something that should be fixed?
(It looks like this could be fixed by only removing changesets if they exist since e.g. at least 3 days)
Thanks.
The text was updated successfully, but these errors were encountered:
Ten0
linked a pull request
Aug 8, 2024
that will
close
this issue
First, thanks for sharing this.
I'm wondering what in the code guarantees that I'm not deleting a changeset before the related deployment from the aws CLI on a separate process manages to read the result of the creation of that changeset.
From reading the code, unless I'm mistaken, it seems that it may instantly delete any changeset that was just created, possibly not letting the time to whoever created it to collect its status first.
This means it may cause concurrent deployments to fail.
Am I mistaken, or is that something that should be fixed?
(It looks like this could be fixed by only removing changesets if they exist since e.g. at least 3 days)
Thanks.
The text was updated successfully, but these errors were encountered: