Resource History API
This guide covers resource-specific details for version history tracking. For general information about the Version History API, see Version History API.
Overview
Marketplace Resources have comprehensive version tracking that captures all modifications to resource configuration, state, and metadata.
Endpoints
1 2 3 4 5 | |
See Version History API for query parameters and response format details.
Tracked Fields
The following resource fields are tracked in version history:
| Field | Description |
|---|---|
name |
Resource display name |
description |
Resource description |
slug |
URL-friendly identifier |
state |
Current state (Creating, OK, Erred, etc.) |
limits |
Resource quotas and limits |
attributes |
Offering-specific attributes |
options |
User-configurable options |
cost |
Current monthly cost |
end_date |
Scheduled termination date |
downscaled |
Whether resource is downscaled |
restrict_member_access |
Access restriction flag |
paused |
Whether resource is paused |
plan |
Associated pricing plan |
Example Response
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 | |
Actions That Create History
The following operations create version history entries:
| Action | Revision Comment |
|---|---|
| Resource update | Updated via REST API |
set_slug |
Slug changed to |
set_downscaled |
Downscaled changed to |
set_paused |
Paused changed to |
set_restrict_member_access |
Restrict member access changed to |
Django Admin Interface
The ResourceAdmin class inherits from VersionAdmin, providing a "History"
button in the Django admin interface. Staff users can:
- View all versions of a resource
- Compare differences between versions
- See who made each change and when
- Revert to a previous version (if needed)
Access the admin history at:
1 | |
Use Cases
Debugging Configuration Issues
When a resource behaves unexpectedly, check its history to see what changed:
1 2 | |
Investigating Cost Changes
Track when and why resource costs changed by filtering history:
1 2 3 | |
Point-in-Time Analysis
Check resource state before an incident:
1 2 3 | |
Related Documentation
- Version History API - General version history documentation
- Resource Actions - Custom resource actions
- Waldur Permissions - Permission system details