RDC Cloud 1.3.0 — Envault and live container scaling

Manage application secrets with EnvaultCopy Anchor Link

Envault Manager gives your team a central place to manage application secrets.

• Secret Groups keep separate values for environments such as development and production.
• Shared Secret stores reusable values referenced with ${shared.group.environment.KEY}.
• Workspace Secret supplies common defaults for Container Engine applications in the workspace.

Import secrets from a .env file or JSON, preview the keys before saving, and reveal or edit values inline. You can save multiple edits together and reveal or hide all values in the selected scope.

In a container's environment settings, use Link Envault to select a group and environment. Linking does not restart the container; redeploy to apply the linked values. A plain restart does not refresh secrets.

Read the Envault guide.

Run local commands with Envault secretsCopy Anchor Link

Bring Envault configuration into your development workflow with the RDC CLI.

Use rdc secret configure to select a secret group and environment. Then run a command with its resolved values:

rdc secret runtime -- npm run dev

The command receives secrets as environment variables without creating a .env file. When you need a file, rdc secret download supports dotenv and JSON output. Keep downloaded secrets out of version control.

Read the Envault CLI guide.

Manage access with categorized rolesCopy Anchor Link

IAM now groups roles by product and responsibility, making it easier to grant the access a teammate needs.

Review directly assigned roles alongside inherited access when managing workspace and project members. Console actions reflect the selected account's effective permissions.

Review workspace access and roles.

Review Envault activity in AuditCopy Anchor Link

The workspace Audit page now records Envault activity, including secret changes, explicit reveals, imports, and CLI exports.

Review who performed an action, its target, time, and outcome. Filter by outcome and load older records to investigate earlier activity. Access to the page requires audit viewing permission.

History includes secret names and revision information, but never secret values. This first release covers Envault and does not restore previous values.

Read the Audit guide.

Change container CPU and memory without redeployingCopy Anchor Link

Open a container's General settings and choose Change plan to compare CPU, memory, and hourly price before applying a new plan.

For supported running application containers, the change updates resource limits without restarting or recreating the container. Existing container files and persistent volumes remain in place. Storage capacity and server placement do not change.

Reducing memory requires enough headroom for current usage; a smaller plan can be rejected if it cannot accommodate the workload. Plan availability and the required permissions are shown in Console.

Read about changing CPU and memory.

Explore resource usage and network trafficCopy Anchor Link

Resource metrics now include container CPU and memory usage, plus inbound and outbound network traffic for containers, Redis, and PostgreSQL.

Choose a time range and inspect individual points to understand how usage changes. Redis overview charts also show memory usage and connections. Missing samples are distinguished from measured zero values.

Network charts show resource traffic rates, including internal communication; they are not a billable transfer report.

Learn about network metrics.