Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Health checks fail when using the new publish to elastic beanstalk interface #749

Open
ashovlin opened this issue Jan 23, 2023 · 1 comment
Open

Health checks fail when using the new publish to elastic beanstalk interface #749

ashovlin opened this issue Jan 23, 2023 · 1 comment
Labels
bug This issue is a bug. p2 This is a standard priority issue queued

Comments

@ashovlin
Copy link
Member

ashovlin commented Jan 23, 2023 •
edited
Loading

Describe the bug

See aws/aws-toolkit-visual-studio#311. Creating a separate issue on this repo as the root cause is likely in the AWS Deploy Tool for .NET CLI which drives the new Visual Studio experience.

We should review differences in packaging between the legacy deployment experience and the new one and how that interacts with health checks.
@ashovlin ashovlin added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jan 23, 2023
@ashovlin ashovlin mentioned this issue Jan 23, 2023
Open
@ashishdhingra ashishdhingra added p1 This is a high priority issue queued and removed needs-triage This issue or PR still needs to be triaged. labels Feb 17, 2023
@ashishdhingra ashishdhingra added p2 This is a standard priority issue and removed p1 This is a high priority issue labels May 19, 2023
@sethreno
Copy link

Hello,
I think I'm running into this bug. I see it was changed from p1 to p2. Is there a known workaround?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug This issue is a bug. p2 This is a standard priority issue queued
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sethreno @ashovlin @ashishdhingra