Why is "Create new Elastic Beanstalk application" grayed-out?

[rmasonjr]

Under "Publish to Existing Target" it wants to Create a new Elastic Beanstalk application.
I dont want a new one, I want to just deploy over the existing one, so I hit "Edit Settings"

Why is the checkbox grayed-out so I can edit the settings?

[ScottDellinger]

@rmasonjr I'm guessing because you are on the Publish to Existing Target tab and are looking at the settings for an existing system. That option becomes available for new apps.

[rmasonjr]

Well, when I tried to publish to new target, it says the application name is already in use:

So how do I deploy an existing app to an existing target?
Why would I want to create a new application each time I deploy? I literally want to update the existing app.

[ScottDellinger]

The interface may be confusing, I guess. If you want to publish to the existing app, that's the one you select and it will publish to the existing app.

…

On Wed, Jun 12, 2024, 7:28 p.m. rmasonjr ***@***.***> wrote: Well, when I tried to publish to new target, it says the application name is already in use: image.png (view on web) <https://github.com/aws/aws-toolkit-visual-studio/assets/11462627/85679603-35de-4871-a982-714526925ab9> So how do I deploy an existing app to an existing target? Why would I want to create a new application each time I deploy? I literally want to update the existing app. — Reply to this email directly, view it on GitHub <#429 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD3TDJCKIEKTP72QBZCN77LZHDYSVAVCNFSM6AAAAABJHELKA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRUGE4DCOBSG4> . You are receiving this because you commented.Message ID: ***@***.***>

[rmasonjr]

Thanks - I started completely over and was eventually able to create a target that allows me to redeploy my app.

[awschristou]

Hi @rmasonjr , thank you for reaching out. I can see how this would be confusing. If you deploy to the existing target, it will deploy to that existing Beanstalk Application. The configuration just happens to have the text "Create new ...". I've filed a ticket with the deploy tool that powers the Publish to AWS experience, to see if this can be improved.