Conversation
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
1 participant
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.
This pull request updates how the Swagger UI component determines which OGC API server base URL to use, adding support for environments with IAM (Identity and Access Management) enabled. It introduces a new environment variable to control this behavior and adjusts the logic accordingly.
Configuration and environment variable changes:
ZOO_IAM_ENABLEDenvironment variable to the Nuxt public runtime config innuxt.config.ts, allowing the app to detect if IAM is enabled.Swagger UI server URL resolution logic:
components/SwaggerUI.vueto check ifZOO_IAM_ENABLEDis set to'true'. If so, it always uses the static fallback URL for the OGC API server, bypassing the per-user server base resolution. If not, it retains the previous behavior of resolving the per-user server base URL.