Database Snapshots

Database Snapshots are point in time backups of a database instance. This class inherits from TopLevelResource and has direct access to the resource’s database object. The following attributes are directly accessible:

attr resource_id:
 The primary resource identifier that takes the form of a prefix followed by numbers and letters
attr organization_service_id:
 The ID of the parent organization service (cloud)
attr region_name:
 The region that the snapshot resides in
attr snapshot_id:
 The provider ID of the snapshot
attr name:The name of the volume
attr instance_resource_id:
 The resource ID of the instance this snapshot was created from
attr snapshot_type:
 The type of snapshot (manual vs automatic)
attr state:The current lifecycle state of the snapshot
attr availability_zone:
 The zone where the snapshot lives
attr create_time:
 The time when the snapshot creation was launched
attr port:The port that the database instance listens on
attr engine:The database engine that the instance was configured to use
attr engine_version:
 The engine version
attr size:The size in gigabytes of the volume
attr progress:The progress of the snapshot creation
attr master_username:
 The master account associated with the instance
attr license:The license used by the instance
attr public:Denotes if the snapshot is publicly available
class DivvyResource.Resources.databasesnapshot.DatabaseSnapshot(resource_id)

Bases: DivvyResource.Resources.toplevelresource.TopLevelResource

delete(user_resource_id=None)
Delete this resource. If wrapped in a with JobQueue() block, this will queue the deletion job to the wrapped queue, otherwise it
calls immediately.
get_date_created()

Retrieve the time from the provider that this resource was created (if available).

static get_db_class()
get_parent_resource_id()
static get_provider_id_field()
static get_resource_type()
get_state()

Retrieve the route state

get_supported_actions()
handle_resource_created(user_resource_id=None, project_resource_id=None)

This should be called when a resource is created/discovered after the basic data is added to the database. This gives an opportunity for post-addition hooks (assignment to groups, alerts, etc)

handle_resource_destroyed(user_resource_id=None)

This should be called when a resource is destroyed before the basic data is removed from the database. This gives an opportunity for pre-destruction hooks (removal from projects/groups, alerts, etc)

handle_resource_modified(resource, *args, **kwargs)

This should be called when a resource is modified after the new data has been updated in the DB session This gives an opportunity for post-modification hooks

snapshot
top_level_resource = True

Database snapshot operations