Added config for base path for web UI #170
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added
FLAGR_WEB_PREFIX
env so it is possible to serve the static web UI from another path different to/
Motivation and Context
For example, if deploying flagger in ECS behind and ELB it wouldn't be possible to deploy Flagr anywhere but in the
/*
listener since the Web UI is served in/
and the API in/api/v1
, this would allow to server the UI from/web/flagr/*
for example.How Has This Been Tested?
Built the code in a docker image, set the environment variable to
/web/flagr
and the UI was loading from that prefixTypes of changes
Checklist: