Hello Railway Support,

I need help safely rotating Postgres credentials for a production project.

Project/environment:

• Project: confident-love
• Environment: production
• Database service: Postgres
• App services using DATABASE_URL:
  • grand-ai-office / web service
  • gaio-devops-agent

Issue:

A partial internal DATABASE_URL was accidentally exposed in a private assistant/operator chat. The URL uses Railway private networking, and no public database URL was exposed, but I still want to rotate the database credentials properly as a security maintenance item.

Important context:

• Production is currently healthy.
• Postgres is healthy.
• I do not want to delete or recreate the database.
• I do not want to manually edit DATABASE_URL unless Railway confirms that is the supported method.
• I do not want to print or reveal the existing DATABASE_URL value again.
• I looked in the Railway UI but did not find a clear managed Postgres credential rotation option.

Request:

Please confirm the safest Railway-supported way to rotate/regenerate the Postgres password or DATABASE_URL credentials for this managed Postgres service.

Specific questions:

1. Is there a supported credential rotation button/path for managed Postgres?
2. Will DATABASE_URL references on dependent services update automatically after rotation?
3. Do dependent services need to be redeployed after rotation?
4. If the UI does not expose a rotation option, can Railway support perform or guide the rotation?
5. What is the safest order of operations to avoid production downtime?

Thank you.