Add a feature that labels all resources--but only once.
Today you can do that with Cloud Scheduler, but after the first mass-labeling, we usually do not want to do it again because then we are spending money on reading the same labels daily.
This could be done by using curl on a new endpoint /label_all_resources at the end of the deployment script.
This endpoint would just do the same as /schedule but on all resource types.
Add a feature that labels all resources--but only once.
Today you can do that with Cloud Scheduler, but after the first mass-labeling, we usually do not want to do it again because then we are spending money on reading the same labels daily.
This could be done by using curl on a new endpoint
/label_all_resourcesat the end of the deployment script.This endpoint would just do the same as
/schedulebut on all resource types.