I hit this problem today on a rocky platform. I had to patch the PoolMember resource to make the stack deletion successful. Simple try/except on ValueError, as is done in other methods. Should I push this simple patch, even if it doesn't fix the root problem (more complex to fix)?
Hi!
I hit this problem today on a rocky platform. I had to patch the PoolMember resource to make the stack deletion successful. Simple try/except on ValueError, as is done in other methods. Should I push this simple patch, even if it doesn't fix the root problem (more complex to fix)?