Deployment Freezes

Block deployments during specific time windows.

What is a Deployment Freeze?

A deployment freeze prevents deployments during configured time periods:

Common Use Cases

Use Case	Freeze Type	Example
Holiday freeze	One-time	Dec 20 - Jan 2
Change freeze	One-time	During audit
Nightly maintenance	Recurring daily	2 AM - 6 AM
Weekend freeze	Recurring weekly	Sat-Sun
Month-end freeze	Recurring monthly	Last 3 days

Freeze Types

One-Time Freeze

Blocks deployments during a specific date range:

┌─────────────────────────────────────────────────────────────┐
│  One-Time Freeze: Holiday Freeze 2024                       │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Start: December 20, 2024 00:00                             │
│  End:   January 2, 2025 23:59                               │
│                                                             │
│  Status: ● Active (5 days remaining)                        │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Recurring Freeze

Repeats on a schedule:

Recurrence	Description	Example
Daily	Same time every day	2 AM - 6 AM nightly
Weekly	Specific days each week	Weekends only
Monthly	Specific days each month	Last 3 days
Yearly	Same dates each year	Dec 20 - Jan 2

Creating a Freeze

Via Lens UI

┌─────────────────────────────────────────────────────────────┐
│  Create Deployment Freeze                                   │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Name *                                                     │
│  [Holiday Freeze 2024                  ]                    │
│                                                             │
│  Description                                                │
│  [No deployments during holiday season ]                    │
│                                                             │
│  ─────────────────────────────────────────────────────────  │
│                                                             │
│  Freeze Type:                                               │
│  ● One-Time                                                 │
│  ○ Recurring                                                │
│                                                             │
│  Start Date/Time *                                          │
│  [2024-12-20] [00:00]                                       │
│                                                             │
│  End Date/Time *                                            │
│  [2025-01-02] [23:59]                                       │
│                                                             │
│  ─────────────────────────────────────────────────────────  │
│                                                             │
│  Scope (leave empty for global freeze):                     │
│  Tenant:      [All                  ▼]                      │
│  Solution:    [All                  ▼]                      │
│  Environment: [Production           ▼]                      │
│                                                             │
│  ☑ Enabled                                                  │
│                                                             │
│                                     [Cancel]  [Create]      │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Via REST API

Deployment freezes are managed through the /api/v1/deployment-freezes endpoint (or the Lens UI). There is no mantisctl freeze subcommand.

# Create a one-time freeze scoped to an environment
curl -X POST "$MANTIS_URL/api/v1/deployment-freezes" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Holiday Freeze 2024",
    "environment_id": "<environment-id>",
    "start_time": "2024-12-20T00:00:00Z",
    "end_time": "2025-01-02T23:59:59Z"
  }'

# Create a recurring daily freeze
curl -X POST "$MANTIS_URL/api/v1/deployment-freezes" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Nightly Maintenance",
    "start_time": "2024-06-01T02:00:00Z",
    "end_time": "2024-06-01T06:00:00Z",
    "recurrence_type": "daily"
  }'

Supported recurrence_type values are daily, weekly, monthly, and yearly; omit the field for a one-time freeze.

Time zones

A freeze’s start_time and end_time are wall-clock times in the freeze’s own zone, named by the optional timezone field. It takes an IANA name and defaults to UTC:

curl -X POST "$MANTIS_URL/api/v1/deployment-freezes" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Nightly Maintenance",
    "start_time": "2024-06-01T02:00:00",
    "end_time": "2024-06-01T06:00:00",
    "timezone": "America/New_York",
    "recurrence_type": "daily"
  }'

Wall-clock is what makes a recurring window survive a daylight-saving change: the freeze above stays 02:00–06:00 in New York on both sides of the shift, rather than drifting an hour. A value that carries an offset — 2024-06-01T02:00:00Z, or +02:00 — names an instant instead, and is converted into the freeze’s zone before it is stored. Responses return these fields without a trailing Z, because they are not UTC.

recurrence_end_date is read the same way, and applies only to recurring freezes; a one-time freeze that sets it is refused. An occurrence that has already started runs to the end of its window even if the end date falls partway through.

Freeze Scope

Global Freeze

Blocks all deployments across the system:

# No tenant_id/solution_id/environment_id = global freeze
curl -X POST "$MANTIS_URL/api/v1/deployment-freezes" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "System Maintenance",
    "start_time": "2024-06-15T22:00:00Z",
    "end_time": "2024-06-16T06:00:00Z"
  }'

Scoped Freeze

Target specific resources:

Scope Level	Blocks
Tenant	All deployments for the tenant
Solution	All deployments of the solution
Environment	All deployments to the environment
Combined	Only matching combinations

Scope a freeze by setting one or more of tenant_id, solution_id, and environment_id on the create request:

// Production-only freeze
{ "name": "Prod Freeze", "environment_id": "<env-id>", "start_time": "...", "end_time": "..." }

// Specific solution in production
{ "name": "Portal Freeze", "solution_id": "<solution-id>", "environment_id": "<env-id>", "start_time": "...", "end_time": "..." }

// Tenant-specific freeze
{ "name": "Acme Freeze", "tenant_id": "<tenant-id>", "start_time": "...", "end_time": "..." }

Recurring Configuration

Daily Freeze

┌─────────────────────────────────────────────────────────────┐
│  Recurring Freeze: Daily                                    │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Time Window:                                               │
│  Start Time: [02:00]  End Time: [06:00]                     │
│                                                             │
│  ┌───────────────────────────────────────────────────────┐  │
│  │ Freeze is active from 02:00 to 06:00 every day        │  │
│  └───────────────────────────────────────────────────────┘  │
│                                                             │
│  Recurrence End Date (optional):                            │
│  [2025-12-31]                                               │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Weekly Freeze

┌─────────────────────────────────────────────────────────────┐
│  Recurring Freeze: Weekly                                   │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Days of Week:                                              │
│  ☐ Monday  ☐ Tuesday  ☐ Wednesday  ☐ Thursday               │
│  ☐ Friday  ☑ Saturday  ☑ Sunday                             │
│                                                             │
│  Time Window:                                               │
│  Start Time: [00:00]  End Time: [23:59]                     │
│                                                             │
│  ┌───────────────────────────────────────────────────────┐  │
│  │ Freeze is active all day on Saturday and Sunday       │  │
│  └───────────────────────────────────────────────────────┘  │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Monthly Freeze

┌─────────────────────────────────────────────────────────────┐
│  Recurring Freeze: Monthly                                  │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Days of Month:                                             │
│  [29, 30, 31                          ]                     │
│  Last 3 days of each month                                  │
│                                                             │
│  Time Window:                                               │
│  Start Time: [00:00]  End Time: [23:59]                     │
│                                                             │
│  ┌───────────────────────────────────────────────────────┐  │
│  │ Freeze is active on days 29, 30, 31 of each month     │  │
│  └───────────────────────────────────────────────────────┘  │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Freeze List View

┌─────────────────────────────────────────────────────────────┐
│  Deployment Freezes                                         │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  [+ New Freeze]        Filter: [All         ▼]              │
│                                                             │
│  Active Freezes:                                            │
│  ┌─────────────────┬──────────────┬───────────┬──────────┐ │
│  │ Name            │ Scope        │ Type      │ Status   │ │
│  ├─────────────────┼──────────────┼───────────┼──────────┤ │
│  │ Holiday 2024    │ Production   │ One-time  │ ● Active │ │
│  │ Weekend Freeze  │ Global       │ Weekly    │ ● Active │ │
│  │ Nightly Maint.  │ All          │ Daily     │ ○ Inactive│ │
│  └─────────────────┴──────────────┴───────────┴──────────┘ │
│                                                             │
│  Upcoming Freezes:                                          │
│  ┌─────────────────┬──────────────┬──────────────────────┐ │
│  │ Name            │ Scope        │ Starts               │ │
│  ├─────────────────┼──────────────┼──────────────────────┤ │
│  │ Q1 Audit Freeze │ All          │ Jan 15, 2025         │ │
│  └─────────────────┴──────────────┴──────────────────────┘ │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Freeze Behavior

Deployment Blocked

When a freeze is active:

┌─────────────────────────────────────────────────────────────┐
│  Deployment Blocked                                         │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  ⚠ Cannot deploy: Active deployment freeze                 │
│                                                             │
│  Freeze: Holiday Freeze 2024                                │
│  Scope: Production                                          │
│  End Time: January 2, 2025 23:59                            │
│                                                             │
│  ┌───────────────────────────────────────────────────────┐  │
│  │ Deployments to Production are blocked until the       │  │
│  │ freeze ends. Contact admin for emergency override.    │  │
│  └───────────────────────────────────────────────────────┘  │
│                                                             │
│                  [View Freeze]  [Request Override]          │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Scope Matching

A freeze blocks a deployment if ALL its non-null scopes match:

Freeze Scope	Deployment Scope	Blocked?
Tenant: Acme	Tenant: Acme	Yes
Tenant: Acme	Tenant: Beta	No
Environment: Prod	Any to Prod	Yes
Solution: Portal, Env: Prod	Portal to Prod	Yes
Solution: Portal, Env: Prod	Portal to Staging	No

Override System

Requesting an Override

For emergencies, request a freeze override:

┌─────────────────────────────────────────────────────────────┐
│  Request Freeze Override                                    │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  Freeze: Holiday Freeze 2024                                │
│  Deployment: customer-portal v1.4.1 to Production           │
│                                                             │
│  Reason for Override *                                      │
│  [Critical security patch - CVE-2024-XXXX requires         ]│
│  [immediate deployment to fix authentication bypass         ]│
│                                                             │
│  ┌───────────────────────────────────────────────────────┐  │
│  │ Override requests are logged and audited.             │  │
│  │ Only users with override permission can proceed.      │  │
│  └───────────────────────────────────────────────────────┘  │
│                                                             │
│                                   [Cancel]  [Override]      │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Override Record

Overrides are permanently recorded:

┌─────────────────────────────────────────────────────────────┐
│  Freeze Overrides: Holiday Freeze 2024                      │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│  ┌─────────────────┬────────────────┬──────────────────┐   │
│  │ Deployment      │ Overridden By  │ Reason           │   │
│  ├─────────────────┼────────────────┼──────────────────┤   │
│  │ portal v1.4.1   │ alice          │ Security patch   │   │
│  │ auth v2.1.1     │ bob            │ Critical bug fix │   │
│  └─────────────────┴────────────────┴──────────────────┘   │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Via REST API

Freeze override is requested per deployment via the override_freeze and override_reason fields on the create request (requires the deployments:override_freeze permission, which can be granted to any role — not exclusively admin). The mantisctl deployment create command does not expose these flags.

curl -X POST "$MANTIS_URL/api/v1/deployments" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "solution_id": "<solution-id>",
    "environment_id": "<environment-id>",
    "override_freeze": true,
    "override_reason": "Critical security patch CVE-2024-XXXX"
  }'

Managing Freezes

List Freezes

# List all freezes (paginated)
curl "$MANTIS_URL/api/v1/deployment-freezes" \
  -H "Authorization: Bearer $TOKEN"

# List only currently-active freezes
curl "$MANTIS_URL/api/v1/deployment-freezes/active" \
  -H "Authorization: Bearer $TOKEN"

Update Freeze

# Extend a freeze (PUT with the fields to change, by freeze ID)
curl -X PUT "$MANTIS_URL/api/v1/deployment-freezes/<freeze-id>" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "end_time": "2025-01-05T23:59:59Z" }'

Delete Freeze

# Delete a freeze (by freeze ID)
curl -X DELETE "$MANTIS_URL/api/v1/deployment-freezes/<freeze-id>" \
  -H "Authorization: Bearer $TOKEN"

Checking Freeze Status

Before Deployment

# Check whether a deployment would be blocked
curl "$MANTIS_URL/api/v1/deployment-freezes/check?solution_id=<solution-id>&environment_id=<environment-id>" \
  -H "Authorization: Bearer $TOKEN"

If a freeze is active for the target scope, creating a deployment is blocked with a 409 (DEPLOYMENT_FROZEN) error; the deployment preview does NOT check active freezes (its warnings field only reports offline/stale targets). Use GET /api/v1/deployment-freezes/check with the relevant solution_id/environment_id to test whether a deployment would be blocked. (There is no freeze_status field on the preview response.)

List Active Freezes

# List all active freezes
curl "$MANTIS_URL/api/v1/deployment-freezes/active" \
  -H "Authorization: Bearer $TOKEN"

Best Practices

1. Plan Freezes in Advance

Schedule freezes before they’re needed:

# Schedule a freeze 2 weeks early
curl -X POST "$MANTIS_URL/api/v1/deployment-freezes" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Q1 Audit",
    "start_time": "2025-01-15T00:00:00Z",
    "end_time": "2025-01-20T23:59:59Z"
  }'

2. Use Appropriate Scope

Avoid global freezes when possible:

Situation	Recommended Scope
Holiday season	Production only
Tenant audit	Specific tenant
Solution upgrade	Specific solution
System maintenance	Global (only when necessary)

3. Document Override Policy

Define when overrides are acceptable:

## Override Policy

Overrides are permitted for:
- Security vulnerabilities (CVE)
- Production-breaking bugs
- Compliance requirements

Required for override:
- Approval from on-call lead
- Documented justification
- Post-deployment verification

4. Review Recurring Freezes

Periodically audit recurring freezes:

• Are they still needed?
• Is the schedule still appropriate?
• Should scope be adjusted?

5. Communicate Freezes

Notify teams of upcoming freezes:

Deployment Freeze Notice:
- Holiday Freeze: Dec 20 - Jan 2
- Scope: Production environment
- Override: Contact on-call lead

Troubleshooting

Freeze Not Blocking

Cause: Scope doesn’t match deployment

Solution:

1. Check freeze scope settings
2. Verify environment/solution/tenant matches
3. Confirm freeze is enabled

Recurring Freeze Not Activating

Cause: Time zone or configuration issue

Solution:

1. Check the freeze’s timezone field — the window is wall-clock in that zone, and it defaults to UTC, so a window entered in local time without setting it fires at the wrong hour
2. Check days-of-week/month configuration; each recurrence type reads only its own fields, and setting one it does not read is refused rather than ignored
3. Confirm recurrence end date hasn’t passed

Cannot Override Freeze

Cause: Insufficient permissions

Solution:

1. Check if user has override permission
2. Contact administrator for emergency access
3. Request role upgrade if needed regularly

Next Steps

• Tags - Organize resources
• Audit Logs - Track system changes