Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

GoogleChromePolicyVersionsV1PolicyApiLifecycle

import type { GoogleChromePolicyVersionsV1PolicyApiLifecycle } from "https://googleapis.deno.dev/v1/chromepolicy:v1.ts";

Lifecycle information.

interface GoogleChromePolicyVersionsV1PolicyApiLifecycle {
deprecatedInFavorOf?: string[];
description?: string;
endSupport?: GoogleTypeDate;
policyApiLifecycleStage?:
| "API_UNSPECIFIED"
| "API_PREVIEW"
| "API_DEVELOPMENT"
| "API_CURRENT"
| "API_DEPRECATED";
scheduledToDeprecatePolicies?: string[];
}

§Properties

§
deprecatedInFavorOf?: string[]
[src]

In the event that this policy was deprecated in favor of another policy, the fully qualified namespace(s) of the new policies as they will show in PolicyAPI. Could only be set if policy_api_lifecycle_stage is API_DEPRECATED.

§
description?: string
[src]

Description about current life cycle.

§
endSupport?: GoogleTypeDate
[src]

End supporting date for current policy. Attempting to modify a policy after its end support date will result in a Bad Request (400 error). Could only be set if policy_api_lifecycle_stage is API_DEPRECATED.

§
policyApiLifecycleStage?: "API_UNSPECIFIED" | "API_PREVIEW" | "API_DEVELOPMENT" | "API_CURRENT" | "API_DEPRECATED"
[src]

Indicates current life cycle stage of the policy API.

§
scheduledToDeprecatePolicies?: string[]
[src]

Corresponding to deprecated_in_favor_of, the fully qualified namespace(s) of the old policies that will be deprecated because of introduction of this policy. This field should not be manually set but will be set and exposed through PolicyAPI automatically.