You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Hugo 27c432a748 feat(scheduler): Drop completed job runs as they complete ... Before this change, upon the completion of a job run, the scheduler would update a job_run entry with the completed status as well as the number of objects affected by the run. Additionally, we then had a cleaner job whose scope was deleting these completed entries from job_run. This commit changes this design to drop the cleaner job the and rolls its functionality directly into the scheduler. Now, when any given job run is complete, the scheduler will automatically delete it from the job_run table itself. In addition, the completed status has been removed as a valid status as it is not set anymore. This change follows a decision that given the data in these job_run entries is already being deleted by the cleaner job, updating its state when a job completes just to have it deleted is not efficient. Additionally, no use-case for this data was surfaced.		1 year ago
..
api	feat(handlers/host_catalogs): Support plugin host catalog worker filter	1 year ago
auth/v1	feat: Add support for capturing URL actions in request info (#5044)	2 years ago
custom_options	Resolve aliases prior to subtype attribute transforming interceptor (#4379)	2 years ago
servers	feat(proto): define storage bucket state in worker status	2 years ago
storage	feat(scheduler): Drop completed job runs as they complete	1 year ago
tokens/v1	[COMPLIANCE] License changes (#3567)	3 years ago