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

Allow setting "/" path with the lowest priority #663

Closed
iamhopaul123 opened this issue Feb 14, 2020 · 0 comments · Fixed by #748
Closed

Allow setting "/" path with the lowest priority #663

iamhopaul123 opened this issue Feb 14, 2020 · 0 comments · Fixed by #748
Assignees
Labels
area/manifest Issues about infrastructure-as-code templates.

Comments

@iamhopaul123
Copy link
Contributor

iamhopaul123 commented Feb 14, 2020

Now, for each application the path is set to be /{appName} or /{appName}/*. However, it would be great to allow users to be able to set a default "/" path in manifest and "/*" for the rule with the lowest priority.

Use case will be:

I have only one application and would like

"12345.eb.wutuper.amazon.com/“ > front-end
"12345.eb.wutuper.amazon.com/api" > back-end

@iamhopaul123 iamhopaul123 added the area/manifest Issues about infrastructure-as-code templates. label Feb 14, 2020
@iamhopaul123 iamhopaul123 added this to Backlog in Sprint 🏃‍♀️ via automation Feb 14, 2020
@iamhopaul123 iamhopaul123 changed the title Allow setting default "/" path with the lowest priority. Allow setting default "/" path with the lowest priority Feb 14, 2020
@iamhopaul123 iamhopaul123 changed the title Allow setting default "/" path with the lowest priority Allow setting "/" path with the lowest priority Feb 14, 2020
@SoManyHs SoManyHs moved this from Backlog to In progress in Sprint 🏃‍♀️ Feb 24, 2020
Sprint 🏃‍♀️ automation moved this from In progress to Pending release Mar 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/manifest Issues about infrastructure-as-code templates.
Projects
Sprint 🏃‍♀️
  
Pending release
Development

Successfully merging a pull request may close this issue.

2 participants