Warning
🚧 Work in Progress: This page is currently under construction. Content may be incomplete or subject to change. To contribute, see the contribution guide.
Production Environment
The production environment serves real end users and business processes. Changes require a change ticket and adherence to the maintenance window policy.
Access
Warning
Restricted access: Production access is restricted. All access requires justification and must be requested via ServiceNow. Direct database access in production is prohibited except in declared P1 incidents.
| Resource | Access method | Who |
|---|---|---|
| GCP project (prod) | Entra ID SSO | Senior engineers + squad leads only |
| Systems | Per-system credentials via Entra ID | Business users (by role) |
| Deployment | GitHub Actions + manual approval | Change ticket + squad lead |
Key URLs and endpoints
| System | Production URL / endpoint |
|---|---|
| patria-tech-docs portal | https://patria-tech-docs.azurestaticapps.net |
| (fill in) | (fill in) |
Deployment policy
All production deployments must:
- Have an open change ticket in ServiceNow
- Be executed within the approved maintenance window — see Maintenance Windows
- Have a documented rollback plan
- Be followed by a 30-minute monitoring period
Emergency deployments (hotfixes): require CTO/CDO approval and must be retroactively registered as an emergency change.
Production access request
- Open a ticket in ServiceNow (category: Access Request → Production)
- Justify the need and expected duration
- Approval by squad lead + security team
- Access is time-limited and logged
Incident response
If something goes wrong in production, follow the Incident Management process immediately.