jamesfredley opened a new pull request, #15618: URL: https://github.com/apache/grails-core/pull/15618
## Summary Adds `https://grails.apache.org` as an additional CORS allowed origin for the Application Forge. **This is necessary in order to move the Application Forge / Start website over to the official Apache Grails website (grails.apache.org).** The existing `https://start.grails.org` origin is preserved (added, not replaced) so the current site keeps working during the transition. ## Changes - **`grails-forge/grails-forge-web-netty/src/main/resources/application.yml`** - Adds a new env-var-backed allowed-origin entry `` alongside the existing `CORS_ALLOWED_ORIGIN` entry. The default value ensures the apache origin is allowed even if the env var is unset. - **All five forge deployment workflows** (`forge-deploy-snapshot.yml`, `forge-deploy-release.yml`, `forge-deploy-prev.yml`, `forge-deploy-prev-snapshot.yml`, `forge-deploy-next.yml`) - Each `gcloud run deploy --update-env-vars` line now also sets `CORS_ALLOWED_ORIGIN_APACHE="https://grails.apache.org"` so the new origin is configured explicitly on every deployed Cloud Run service (snapshot, release latest, release versioned, prev, prev-snapshot, next). ## Notes - Pattern mirrors the existing `CORS_ALLOWED_ORIGIN` env var so the per-environment override mechanism stays consistent. - Defense in depth: the apache origin works via either the YAML default or the explicit workflow env var. Hardcoding only in YAML would have worked too, but mirroring the workflow env var keeps deploy-time configuration self-documenting. - Only CORS-related occurrences of `start.grails.org` are touched. `GITHUB_REDIRECT_URL` and `GITHUB_USER_AGENT` references are left as-is - those point to the actual UI URL, not CORS, and the website move is a separate operational step. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
