Repository navigation
fix(pygeoapi): use weaver-api custom domain for server URL and title - #153
Merged
Merged
Conversation
pygeoapi builds every link from server.url, so links still pointed at the Cloud Run run.app URL after the DNS change.
|
Your pull request is automatically being deployed to Dagster Cloud.
|
jacob-a-brown
approved these changes
Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
pygeoapi builds every link from
server.url, not from the host in the request. So after the DNS change, pages loaded onweaver-api.newmexicowaterdata.orgbut every link went back to the Cloud Runrun.appURL.PYGEOAPI_SERVER_URLincloudbuild.yamltohttps://weaver-api.newmexicowaterdata.orgSPEC.mdand the config comments to match