Hello, I have a strange behavior continuously; I deployed a stack without issues, but regardless of the command I want to perform, destroy, up, refresh, the operation generates a lock. It is impossible to go out of this loop.
If I delete the lock anyway, it throws, and the message says there is a ConcurrentUpdateError by the same process; how is it possible? 🤯
Another weird behavior is that the command execution throws a ConcurrentUpdateError, but in the catch block, I receive a CommandError.
Whatever suggestion would be more than appreciated
05/19/2023, 1:30 PM
Can you describe what you are seeing in more detail? It is expected that a lock is taken until the update finishes. Are you saying that after the update succeeds there is still a lock?