A stage's content mutation guard. Its name must be unique across the whole
definition and use lowercase letters, digits, and dashes, starting with a
letter or digit. match.actions must contain at least one action.
match.types intersects the ID criteria. Within the ID criteria, matching
either idRefs or idPatterns is sufficient. Omitted or empty optional
criteria do not constrain the match. idRefs uses typed GuardReads.
Patterns use resource-local document-ID characters and * wildcards.
A release-version pattern is rejected if translating it for a lifecycle
action would broaden it to every document.
predicate is delta-mode GROQ over document, guard, and mutation;
see GUARD_PREDICATE_VARS. Only a strict true allows a matching
mutation. An omitted or empty predicate denies it. metadata resolves
GuardReads into values available as guard.metadata in the predicate.
Engine evaluations are advisory; the Content Lake is the enforcement point.
A stage's content mutation guard. Its name must be unique across the whole definition and use lowercase letters, digits, and dashes, starting with a letter or digit.
match.actionsmust contain at least one action.match.typesintersects the ID criteria. Within the ID criteria, matching eitheridRefsoridPatternsis sufficient. Omitted or empty optional criteria do not constrain the match.idRefsuses typed GuardReads. Patterns use resource-local document-ID characters and*wildcards. A release-version pattern is rejected if translating it for a lifecycle action would broaden it to every document.predicateis delta-mode GROQ overdocument,guard, andmutation; see GUARD_PREDICATE_VARS. Only a stricttrueallows a matching mutation. An omitted or empty predicate denies it.metadataresolves GuardReads into values available asguard.metadatain the predicate. Engine evaluations are advisory; the Content Lake is the enforcement point.