Skip to content

Update canonicalHostname field on proxy status#125

Merged
mattdjenkinson merged 4 commits intomainfrom
chore/update-canonical-hostname-on-proxy
Apr 9, 2026
Merged

Update canonicalHostname field on proxy status#125
mattdjenkinson merged 4 commits intomainfrom
chore/update-canonical-hostname-on-proxy

Conversation

@mattdjenkinson
Copy link
Copy Markdown
Contributor

We need this field in the UI so we can ensure we always show the Datum provided hostname.

scotwells
scotwells previously approved these changes Mar 11, 2026
@zachsmith1
Copy link
Copy Markdown
Contributor

@mattdjenkinson i dont think this will work with the new words based default hostname

@zachsmith1
Copy link
Copy Markdown
Contributor

zachsmith1 commented Mar 11, 2026

or we might need to look into backwards compatibility a bit. for the other PR, I at least made it respect the old route names but it might need to looking into. or maybe just peak into the gateway listeners section and default-https will be there

@zachsmith1
Copy link
Copy Markdown
Contributor

@mattdjenkinson is this needed anymore or did one of my previous PRs fix it?

@mattdjenkinson
Copy link
Copy Markdown
Contributor Author

@zachsmith1 yeah we'll still need this. Why wouldn't it work with the new hostnames?

@mattdjenkinson
Copy link
Copy Markdown
Contributor Author

Screenshot 2026-04-09 at 16 50 27

It's working in staging!

@mattdjenkinson mattdjenkinson merged commit c245180 into main Apr 9, 2026
10 of 11 checks passed
@mattdjenkinson mattdjenkinson deleted the chore/update-canonical-hostname-on-proxy branch April 9, 2026 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants