Support label or metadata based lifecycle rules [270684223]

Assigned

Feature Request

Status Update

No update yet.

Description

au...@adt.com

created issue #1

Feb 24, 2023 10:28PM

Provide the ability to define lifecycle management policies that match based on specific metadata and/or label key:value pairs, so users do not require using creative naming solutions (prefix/suffix) when use cases require having multiple lifecycle policies for mixed object.

This would provider parity with AWS S3 object tagging filters for lifecycle management (

https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html#tagging-other-configs)

Comments

ku...@google.com <ku...@google.com> Feb 27, 2023 06:14AM

Assigned to ku...@google.com.

ku...@google.com <ku...@google.com> #2Feb 27, 2023 03:52PM

Reassigned to gc...@google.com.

Thanks for the report. I will route this to the appropriate internal team and update this when I hear back from them.

al...@google.com <al...@google.com> Mar 23, 2023 10:04PM

Reassigned to jy...@google.com.

va...@google.com <va...@google.com> Sep 5, 2023 07:22AM

Reassigned to su...@google.com.

ky...@redoxengine.com <ky...@redoxengine.com> #3Sep 18, 2023 09:02PM

One more detail, Data Layer event calls from the watch to the phone (running Android 13) do work on if the listener is in an Activity or Fragment.

su...@google.com <su...@google.com> Oct 9, 2023 09:50AM