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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Tell us about your request
Please add --since=TIMESTAMP and/or --tail=LINES options to eb events command.
I would like to follow logs since some timestamp (for example deploy started), similar to kubectl has.
I would also accept --tail=0 option to start following for new entries only.
Additional context
I'm attempting to build CI workflow that starts update an environment and print events as they occur until deploy is finished.
The text was updated successfully, but these errors were encountered:
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request. If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Tell us about your request
Please add
--since=TIMESTAMP
and/or--tail=LINES
options toeb events
command.I would like to follow logs since some timestamp (for example deploy started), similar to kubectl has.
I would also accept
--tail=0
option to start following for new entries only.Additional context
I'm attempting to build CI workflow that starts update an environment and print events as they occur until deploy is finished.
The text was updated successfully, but these errors were encountered: