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
Since its basically the same thing as exciting recipes to add an ssh-key and you can't ssh until that chef run has finished we should just pop the stack monitor so the user knows an action is being run.
The text was updated successfully, but these errors were encountered:
Meh, I'd leave a message saying it's running the update and to wait a few minutes while Opsworks is updating. Maybe even tell them you can view it using the monitor command. It's the sort of command that's more scripty than deploy-like, IMO. My two cents.
yeah my point was more that behind the scenes opsworks is doing exactly the same thing as a deploy or execute_recipes so it seemed like we should have the same behavior.
Since its basically the same thing as exciting recipes to add an ssh-key and you can't ssh until that chef run has finished we should just pop the stack monitor so the user knows an action is being run.
The text was updated successfully, but these errors were encountered: