GCS -LIFE-CYCLE MANAGEMENT, CONDITIONS.

 

 Lifecycle management : In order to use Object Lifecycle management, you define a lifecycle configuration which is specified on a bucket. At the level of GCS allow you to create particular rules to transition data from one storage class to another based on specific conditions. And the conditions could be, for example, an object can be stored in cloud storage for four months and after four months the developers likely not won't be accessing the data frequently. At this point the conditions you set up will be based on timeline. 

You can also move data from standard to nearline or coldline. If the objects is not assessable within the specified lifecycle, it can be moved to archive and you can also delete the object anytime. 

Lifecycle management has help to automate move of objects to a different storage class based on their age. It has delete old version of objects and reduce storage costs. 

CLOUD STORAGE OBJECTS BY SETTING CONDITIONS.

Timeline

Age: Many companies use this condition. Age condition defines the time when the object was created in a bucket and it can be moved from one location to another 80days, 90days, 360days. This works with any class and the actual files. 

Createdbefore : In this case,  you can create a rule in GCS that every previous object that was created before MAY 19TH to transition the object from one storage class to another. 

Multiple rules and Conditions: Another conditions you can set up would be, if the storage class matches any standard, nearline, archive, which the data can be transitioned.  

Versioning: When it comes to the bucket, first you have to delete the object before the bucket. If you're wondering where the object resides after deletion, this is were versioning comes in. You have to explicitly enable the management capability of the bucket because, it will keep multiple version of all the object in the bucket and anytime you try to delete, it will take a back-up and store it in the versioning pool. Versioning will act as your recycle bin.

Pub-sub: It is fully managed real-time messaging system to send auto-alert between independent applications. You can set up a topic that act as a pub-sub resources and then integrate GCS at the level of the topic and then create a subscription within the specific topic then subscribe email. This will give you visibility of the bucket. 

Referencing: Google Documentation.