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 just spent a good few hours chasing strange errors running modules against 2 different AWS accounts. Only to find some very unexpected behavior in pacu.
To reproduce
Open 2 terminals
In terminal 1 run pacu and create a new session named "SESSION1"
In terminal 2 run pacu and create a new session named "SESSION2"
go back to terminal one and hit return and it now says SESSION2 in terminal 1.
The text was updated successfully, but these errors were encountered:
Must be because Pacu is just pulling the "active session" from the same DB. Maybe adding some unique identifier for each CLI session and using that to identify which session and data to be using. Will have to look more into this.
I just spent a good few hours chasing strange errors running modules against 2 different AWS accounts. Only to find some very unexpected behavior in pacu.
To reproduce
Open 2 terminals
In terminal 1 run pacu and create a new session named "SESSION1"
In terminal 2 run pacu and create a new session named "SESSION2"
go back to terminal one and hit return and it now says SESSION2 in terminal 1.
The text was updated successfully, but these errors were encountered: