Skip to content

Conversation

@ulrikandersen
Copy link
Contributor

Description

This PR aims to improve the debug experience when loading remote specification fails by:

  1. Including part of remote spec content in error response from /remote endpoint. Makes it easier to debug why loading a remote spec fails.
  2. Include remote spec name in the error message when decryption fails (Failed to decrypt remote specification auth for framna-docs-local (https://ws.fk.dk/dev/omdeler/api-docs). Perhaps a different public key was used?). Makes it easier to see which remote spec is failing.

Also the log level of 2. is changed to reflect that it is an expected error (e.g. wrong encryption key used).

Screenshots (if appropriate):

Screenshot 2025-02-06 at 09 00 07

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

@ulrikandersen ulrikandersen merged commit 639a319 into develop Feb 6, 2025
7 checks passed
@ulrikandersen ulrikandersen deleted the include-file-content-in-error-message branch February 6, 2025 09:11
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.

2 participants