Big Data Snapshots¶
Big Data Snapshots are point in time backups of a Big Data Instance. An example of this type of instance would be AWS Redshift. This class inherits from TopLevelResource and has direct access to the resource’s database object. The following attributes are directly accessible:
|The primary resource identifier that takes the form of a prefix followed by numbers and letters|
|The ID of the parent organization service (cloud)|
|The region that the snapshot resides in|
|The provider ID of the snapshot|
|attr name:||The name of the snapshot|
|The resource ID of the instance this snapshot was created from|
|The type of snapshot (manual vs automatic)|
|attr state:||The current lifecycle state of the snapshot|
|attr encrypted:||Denotes if the data stored on the snapshot is encrypted|
|The zone where the snapshot lives|
|The time when the snapshot creation was launched|
|attr port:||The port that the database instance listens on|
|attr nodes:||How many nodes are in this cluster|
|The type of instance this snapshot was taken on|
|The name of the master database|
|attr engine:||The database engine that the instance was configured to use|
|The engine version|
|attr size:||The size in gigabytes of the volume|
|attr progress:||The progress of the snapshot creation|
|The master account associated with the instance|
|attr license:||The license used by the instance|
- Delete this resource. If wrapped in a with JobQueue() block, this will queue the deletion job to the wrapped queue, otherwise it
- calls immediately.
Retrieve the time from the provider that this resource was created (if available).
Retrieve the route state
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)
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.
BigData snapshot operations