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.

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

Deploying to an existing Beanstalk has a setting titled "Create new Elastic Beanstalk application" #834

Open
awschristou opened this issue Jun 13, 2024 · 0 comments
Labels
bug This issue is a bug. p2 This is a standard priority issue queued

Comments

@awschristou
Copy link
Contributor

Describe the bug

Using the AWS Toolkit for Visual Studio, a customer has found that one of the deployment configurations has a confusing name.

When you go to redeploy to an existing Beanstalk application, the overall configuration is set up to reference the previously deployed Beanstalk app, however the "CreateNew" setting is marked read-only, visible, and true. It has the display text "Create new Elastic Beanstalk application", which you can see from the linked issue how this could be interpreted in a confusing way.

Here is what the configuration state looks like in the Toolkit for this setting:
image

Expected Behavior

Maybe the configuration needs to have its display text conditionally updated for this scenario. Or maybe its plausible to mark the setting as hidden -- when performing the same redeployment from the command line, this particular setting isn't seen.

Current Behavior

See above

Reproduction Steps

Using the AWS Toolkit for Visual Studio, deploy an app to Beanstalk Linux. Then select that deployment from the "Existing Targets" list, and look at the configuration displayed. See linked issue for screenshots also.

Possible Solution

No response

Additional Information/Context

No response

Version used

1.18.6

Operating System and version

Windows 11

@awschristou awschristou added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Jun 13, 2024
@bhoradc bhoradc added needs-reproduction This issue needs reproduction. p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels Jun 13, 2024
@bhoradc bhoradc added queued and removed needs-reproduction This issue needs reproduction. labels Jun 28, 2024
@ashishdhingra ashishdhingra added needs-reproduction This issue needs reproduction. p1 This is a high priority issue and removed p2 This is a standard priority issue queued labels Jun 28, 2024
@bhoradc bhoradc added queued p1 This is a high priority issue and removed needs-reproduction This issue needs reproduction. p1 This is a high priority issue labels Jun 28, 2024
@bhoradc bhoradc removed their assignment Jun 28, 2024
@ashishdhingra ashishdhingra added p2 This is a standard priority issue and removed p1 This is a high priority issue labels Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. p2 This is a standard priority issue queued
Projects
None yet
Development

No branches or pull requests

3 participants