Replies: 3 comments 1 reply
-
I had assumed that utilizing a URL as the OpenAPI source would automatically recognize updates in the file, but it seems this is not the case. Additionally, I've encountered an issue where this URL becomes cached within GitBook, preventing the updating of OpenAPI blocks since the cached contents of the URL are loaded instead. The only workaround I've found is to clear the cache by appending a query parameter to the URL, such as ?v=1.0.1. @jpreynat, I'm wondering if there's a method to enable live updates from an OpenAPI source (URL) within our blocks? |
Beta Was this translation helpful? Give feedback.
-
The OpenAPI snippet is really useful. We'd love to be able to incorporate updating the source document as part of our CI/CD pipeline (our spec file is currently generated from our source as part of our pipeline). The simplest would be if GitBook could recognize changes in the source URL but having an ability to trigger an update via REST or some other mechanism would also be great (versus having to manually re-upload a new source document) Thank you! |
Beta Was this translation helpful? Give feedback.
-
If you import an OpenAPI file through the Import content dialog instead of through an OpenAPI block, is there any way to update the source, aside from deleting it and reimporting it?
Beta Was this translation helpful? Give feedback.
All reactions