If a user attempts to create a new stack using an invalid environment name, they are displayed an "Environment is invalid" warning that doesn't disappear after the name becomes formatted correctly, and the warning continues to persist on all subsequent pages after the stack is created until the site is refreshed.
I think the warning should disappear by the time the stack is successfully created as the warning is no longer relevant past that point.
Steps to reproduce:
Attempt to create a new stack with an invalid environment name (for example: eqr/production).
Change the environment name to an accepted format (for example: production) and finish creating the stack.
The warning should still display on the following pages visited.
Probably another ticket, but I wonder if we should consider a more descriptive error that specifies the accepted characters for environment_name.
If a user attempts to create a new stack using an invalid environment name, they are displayed an "Environment is invalid" warning that doesn't disappear after the name becomes formatted correctly, and the warning continues to persist on all subsequent pages after the stack is created until the site is refreshed.
I think the warning should disappear by the time the stack is successfully created as the warning is no longer relevant past that point.
Steps to reproduce:
eqr/production
).production
) and finish creating the stack.Probably another ticket, but I wonder if we should consider a more descriptive error that specifies the accepted characters for environment_name.