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.
Tell us about your request
Version label not shown in SNS payload.
Is this request specific to an Elastic Beanstalk platform?
If so, which one(s)?
Beanstalk
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I would like to get a slack notification when a new version has finished deploying with a visible version number. I've tried a postdeploy script, but the old version is shown instead of the current version. I've tried a SNS-Lambda, but the version is not in the event payload.
Are you currently working around this issue?
No
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
It appears the solution would be adding the version number to the event payload
The text was updated successfully, but these errors were encountered:
Community Note
Tell us about your request
Version label not shown in SNS payload.
Is this request specific to an Elastic Beanstalk platform?
If so, which one(s)?
Beanstalk
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I would like to get a slack notification when a new version has finished deploying with a visible version number. I've tried a postdeploy script, but the old version is shown instead of the current version. I've tried a SNS-Lambda, but the version is not in the event payload.
Are you currently working around this issue?
No
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
It appears the solution would be adding the version number to the event payload
The text was updated successfully, but these errors were encountered: