Compartment OCID where the resource is created
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Managed list description
Managed list display name
Provider of the managed list feed
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
Avoid entering confidential information.
Unique identifier that can't be changed after creation
Is this list editable?
The current lifecycle state of the resource
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state. [DEPRECATE]
List of items in the managed list
Type of information contained in the managed list
OCID of the source managed list
System tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. System tags can be viewed by users, but can only be created by the system.
Example: {@code {\"orcl-cloud\": {\"free-tier-retained\": \"true\"}}}
The date and time the managed list was created. Format defined by RFC3339.
The date and time the managed list was last updated. Format defined by RFC3339.
A managed list is a reusable list of parameters that makes it easier to set the scope for detector and responder rules. A ManagedList resource contains the reusable list of parameters, plus metadata for the list.