Embed OpenAPI spec and Swagger UI in main Wave container

[pditommaso]

Why

Until now the Wave OpenAPI spec was shipped as a separate wave/openapi nginx image, built and pushed by typespec.yml on every [release] commit. That meant two images to deploy, two lifecycles to keep in sync, and a docs endpoint that lived outside the main Wave service.

This PR follows the Sched project pattern: the spec is generated as part of the main Gradle build and served directly from the Wave application container at /openapi/.

What changes

Before / after

Aspect	Before	After
OpenAPI docs hosting	dedicated wave/openapi nginx image	bundled in wave/app at /openapi/
Spec generation	typespec.yml workflow on [release]	Gradle task chain on every build
Swagger UI assets	inline CDN scripts in typespec/index.html	served from org.webjars:swagger-ui:5.17.14
Release pipeline	extra ECR push step	none (folded into main image build)

Files

Added

• src/main/resources/swagger-ui-template.html — Swagger UI page, rendered at build time with ${PROJECT_VERSION}.
• src/main/resources/public/openapi/swagger-ui-init.js — Swagger UI bootstrap (externalised for CSP).
• src/main/resources/public/openapi/swagger-ui-overrides.css — minor Swagger UI styling (externalised for CSP).

Modified

• build.gradle — adds swagger-ui webjar dependency and three new Gradle tasks: installTypeSpec → generateOpenApi → generateSwaggerUI, wired into processResources.
• src/main/resources/application.yml — adds static-resource mappings for /openapi/** and /webjars/**.
• src/main/groovy/io/seqera/wave/controller/ServiceInfoController.groovy — drops the @Get("/openapi") redirect (it caused a 301 loop because Micronaut resolves /openapi and /openapi/ to the same route).
• .github/workflows/typespec.yml — keeps TypeSpec validation only; drops AWS/ECR config and the docker build/push step.

Deleted

• typespec/Dockerfile
• typespec/index.html
• typespec/tag-and-push-openapi.sh

How it hangs together

./gradlew processResources
└── generateSwaggerUI         # renders index.html from the template
    └── generateOpenApi       # npx tsp compile .  →  typespec/tsp-output/.../openapi.yaml
        └── installTypeSpec   # npm install

The generated openapi.yaml and index.html, together with the static CSS/JS, end up under build/resources/main/public/openapi/ and are bundled into the JIB image. Micronaut serves them via the /openapi/** static-resource mapping; Swagger UI's JS/CSS comes from the swagger-ui webjar at /webjars/swagger-ui/5.17.14/....

Note on CSP

Wave's response filter sets a strict default-src 'self'; style-src 'self' https://fonts.googleapis.com; ... — no 'unsafe-inline'. The Swagger UI template therefore loads its init script and overrides from same-origin URLs rather than inline <script>/<style> blocks, so no CSP relaxation was needed.

Test plan

• ./gradlew processResources produces build/resources/main/public/openapi/{openapi.yaml,index.html,swagger-ui-init.js,swagger-ui-overrides.css} with the correct version interpolated into index.html.
• ./run.sh, then visit http://localhost:9090/openapi/ — Swagger UI renders, endpoints list loads, /openapi/openapi.yaml returns the spec.
• Browser DevTools Console shows no CSP violations on /openapi/.
• CI: PR build succeeds (no Node setup is added — ubuntu-latest ships with Node, enough for npm install + npx tsp compile .).
• typespec.yml still validates TypeSpec changes on PRs.

---

🤖 Generated with Claude Code