Fix dak-api.html: link to Swagger UI openapi/index.html, remove inline schema cards#199
Fix dak-api.html: link to Swagger UI openapi/index.html, remove inline schema cards#199
Conversation
…k-api.html Co-authored-by: litlfred <662242+litlfred@users.noreply.github.com>
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
Co-authored-by: litlfred <662242+litlfred@users.noreply.github.com>
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
|
@copilot I don't see the request to changes at https://worldhealthorganization.github.io/smart-base/branches/fix-dak-api-html-interface/dak-api.html |
…T/END markers) Co-authored-by: litlfred <662242+litlfred@users.noreply.github.com>
The root cause was a CI re-run issue: when a job is re-run, the Fixed in Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
|
I still don't see changes at https://worldhealthorganization.github.io/smart-base/branches/fix-dak-api-html-interface/dak-api.html |
Co-authored-by: litlfred <662242+litlfred@users.noreply.github.com>
Co-authored-by: litlfred <662242+litlfred@users.noreply.github.com>
Root cause confirmed and fixed in Why it wasn't updating: The IG publisher runs inside a Docker container whose default user creates Fixes:
The next CI run should deploy correctly updated Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
❌ Deployment FailedBranch: Deployment failed. Please check the build log for details. |
|
Build error @copilot |
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
|
It is still not working. See if the commit tags were deployed. Please review all of the commit logs for GH pages, Branch and the deployment logs for the actions to see where it is failing. @copilot |
Co-authored-by: litlfred <662242+litlfred@users.noreply.github.com>
Investigated the full CI/gh-pages chain. Two root causes found and fixed in 1. Wrong deploy target folder (BRANCH_DIR=merge) 2. Docker file ownership blocks dak-api.html writes After the next CI run completes, the changes should be visible at Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
Try to fetch the gh-pages dak-api.html contenturl = 'REDACTED'
|
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
|
Please review the upstream changes, in and propose a merge plan. Please ensure this workflow is only running if it is a dak (deck so that the dak environment variable is true) @copilot |
Co-authored-by: litlfred <662242+litlfred@users.noreply.github.com>
Reviewed upstream changes and applied the merge in Upstream changes from main (PR #202 - Weblate translation support):
Both were already properly gated with DAK gating fix: Changed "Stamp deploy metadata" from Our branch now has all upstream translation steps plus our fixes (BRANCH_DIR for PR events,
|
|
Still .github/workflows/ghbuild.yml conflict @copilot |
The merge conflict is resolved. The workflow file has been rebuilt from main's current HEAD (which includes the Weblate translation steps from PR #202) with only our specific additions applied on top:
The only diff vs main is our 5 additions — no conflicts, no duplicated steps. The two Weblate steps ( |
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
|
Please see if branches directory of gh-paGes is being committed to on feature branch build @copilot |
Yes, the feature branch build is correctly committing to The latest CI run (run
The following files are now live in gh-pages under
Preview URL: https://worldhealthorganization.github.io/smart-base/branches/fix-dak-api-html-interface/dak-api.html |
…e Using the DAK API Co-authored-by: litlfred <662242+litlfred@users.noreply.github.com>
✅ Deployment SuccessfulBranch:
Deployment completed successfully! The site is now live at the URL above. |
|
Analyze upstream and propose how to resolve conflicts before continuing. .github/workflows/ghbuild.yml |
The workflow file has no conflict markers — it's clean. Here's the full diff vs 2 lines changed (the BRANCH_DIR PR-events fix):
64 lines added — 4 new steps, all purely additive after existing steps, none overlapping with main:
Our branch = |
dak-api.htmlwas cluttered with inline ValueSet and Logical Model schema cards, whileopenapi/index.htmlalready provides full Swagger UI over the same schemas. The page structure also buried the OpenAPI link below the usage section.Changes
generate_hub_html_contentno longer emits theValueSet SchemasandLogical Model Schemascard grids (~85 lines of generated HTML per build). All schema browsing is delegated toopenapi/index.html.openapi/index.htmllink) now appears first; "Using the DAK API" usage guidance follows below it.Result
dak-api.htmlnow renders as:openapi/index.htmlwas already generating a correct Swagger UI page (SwaggerUIBundlewith all ValueSet and LogicalModel.openapi.jsonURLs) — no changes needed there.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
worldhealthorganization.github.io/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.