)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"bafa1597802000702ee61ba1ebe870b77bbfc82e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"dea64287_f8a159a1","updated":"2024-09-24 19:28:41.000000000","message":"I\u0027d very much prefer this to be published to a subdirectory on docs.openstack.org","commit_id":"ffbfc857a9d619ccf63d34c527a7d76794ea5b4b"},{"author":{"_account_id":4146,"name":"Clark Boylan","email":"cboylan@sapwetik.org","username":"cboylan"},"change_message_id":"7ad4abdd32796baa474aa6c13559ace49a97eb00","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"aea9428b_2dcb43b8","in_reply_to":"dea64287_f8a159a1","updated":"2024-09-24 21:07:21.000000000","message":"To followup on that the current api reference for openstack apis is hosted at https://docs.openstack.org/api-ref. It seems like we should be able to host similar for openapi specification at a path like https://docs.openstack.org/openapi-specs or similar. One reason to do this is to keep similar content located together for ease of discover and navigation. It also simplifies setup as the docs publishing is already configured (afs volumes, ssl certs, zuul jobs, etc). Additionally, you can pair openapi specs with swagger to provide an experience very similar to the /api-ref content.\n\nIf there is some reason that isn\u0027t technically feasible I would suggest we avoid baking openapi into the domain name at least. The reason for this is at some point in the future we may switch from openapi to some other tool and if that happens not needing to create another domain and migrate things safely without visible impact becomes more difficult. Maybe use something like api-specs.openstack.org and then the tooling is less important and can transition if necessary in the future.","commit_id":"ffbfc857a9d619ccf63d34c527a7d76794ea5b4b"}]}