Swagger updates #4
Merged
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
emondal1026
approved these changes
Jun 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 PR updates Swagger to use a valid tenant if one exists. If no tenant exists and the environment does not use a custom build, it uses the default Swagger for the selected WebAPI version (https://api.ed-fi.org/v${EdFiApiVersion}/api/metadata/data/v3/resources/swagger.json). If no tenant exists and the environment uses a custom build, it displays "No API definition provided." If Swagger is deployed, the tenant management function will invoke the update Swagger function any time a tenant is added or removed. The tenant management function's "Reload" action should be invoked after a tenant is added or removed to prevent errors in Swagger.