[John McCall (lowlydba)]

Resolves #604

Switches PR previews to the pages-staging-scoped-oidc-overturemaps role and adds environment: staging to the cleanup job (deploy already has it).

Blocked: do not mark ready until OvertureMaps/omf-core-data-opentofu#149 is applied.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Max errors	Warnings	Elapsed time
✅ JAVASCRIPT	eslint	33		0		0	22.43s
✅ MARKDOWN	markdownlint	286		0		0	0.54s
✅ SQL	sqlfluff	79		0		0	6.48s

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@10.1.0 --custom-flavor-setup --custom-flavor-linters JAVASCRIPT_ES,MARKDOWN_MARKDOWNLINT,SQL_SQLFLUFF

Show us your support by starring ⭐ the repository

[Copilot]

🔵 Needs a closer look

The blocking trust-policy update in OvertureMaps/omf-core-data-opentofu#149 was inaccessible for verification, and preview deployment and closed-PR cleanup still require validation with the scoped role.

No open issues 🎉

What changed in this PR

Updates documentation PR previews to use the repository-scoped AWS OIDC role, addressing #604 and restricting access to the repository’s preview prefix.

Changes:

• Switches deploy and cleanup workflows to pages-staging-scoped-oidc-overturemaps.
• Adds environment: staging to cleanup to satisfy the scoped role’s trust requirements.

The rollout remains blocked until OvertureMaps/omf-core-data-opentofu#149 is applied.

File	Description
.github/​workflows/​staging_deploy.yaml	Uses the scoped role for preview deployment.
.github/​workflows/​staging_deploy_cleanup.yaml	Uses the scoped role and staging environment for preview cleanup.

_{Review effort: Balanced}