[v8 backport] Expose reverse tunnel address to web ui #10514
Merged
+17
−3
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.
Backport of #10133
webapps v8 backport: gravitational/webapps#616
The ultimate purpose is to show the reverse tunnel address on Help & Support screen on the web UI.
On cloud instances, we use a custom reverse tunnel port for each tenant. In the UI, there is no way to know your reverse tunnel address, which is necessary when adding a trusted cluster.
This PR adds the reverse tunnel address to the GRV_CONFIG object that is injected into the web UI. I added it behind a feature flag to only show on cloud only, should we expose it to everyone?
Note that this field is already publicly exposed via GET [proxy server]/webapi/ping.