Data Source: oci_jms_fleet

This data source provides details about a specific Fleet resource in Oracle Cloud Infrastructure Jms service.

Retrieve a Fleet with the specified identifier.

Example Usage

data "oci_jms_fleet" "test_fleet" {
	#Required
	fleet_id = oci_jms_fleet.test_fleet.id
}

Argument Reference

The following arguments are supported:

• fleet_id - (Required) The OCID of the Fleet.

Attributes Reference

The following attributes are exported:

• approximate_application_count - The approximate count of all unique applications in the Fleet in the past seven days. This metric is provided on a best-effort manner, and isn’t taken into account when computing the resource ETag.
• approximate_installation_count - The approximate count of all unique Java installations in the Fleet in the past seven days. This metric is provided on a best-effort manner, and isn’t taken into account when computing the resource ETag.
• approximate_java_server_count - The approximate count of all unique Java servers in the Fleet in the past seven days. This metric is provided on a best-effort manner, and isn’t taken into account when computing the resource ETag.
• approximate_jre_count - The approximate count of all unique Java Runtimes in the Fleet in the past seven days. This metric is provided on a best-effort manner, and isn’t taken into account when computing the resource ETag.
• approximate_library_count - The approximate count of all unique libraries in the Fleet in the past seven days. This metric is provided on a best-effort manner, and isn’t taken into account when computing the resource ETag.
• approximate_library_vulnerability_count - The approximate count of all unique library vulnerabilities in the Fleet in the past seven days. This metric is provided on a best-effort manner, and isn’t taken into account when computing the resource ETag.
• approximate_managed_instance_count - The approximate count of all unique managed instances in the Fleet in the past seven days. This metric is provided on a best-effort manner, and isn’t taken into account when computing the resource ETag.
• compartment_id - The OCID of the compartment of the Fleet.
• defined_tags - Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {"foo-namespace.bar-key": "value"}. (See Understanding Free-form Tags).
• description - The Fleet’s description.
• display_name - The name of the Fleet.
• freeform_tags - Simple key-value pair that is applied without any predefined name, type, or scope. Exists for cross-compatibility only. Example: {"bar-key": "value"}. (See Managing Tags and Tag Namespaces.)
• id - The OCID of the Fleet.
• inventory_log - Custom Log for inventory or operation log.
  • log_group_id - The OCID of the log group.
  • log_id - The OCID of the log.
• is_advanced_features_enabled - Whether or not advanced features are enabled in this Fleet. Deprecated, use /fleets/{fleetId}/advanceFeatureConfiguration API instead.
• is_export_setting_enabled - Whether or not export setting is enabled in this Fleet.
• operation_log - Custom Log for inventory or operation log.
  • log_group_id - The OCID of the log group.
  • log_id - The OCID of the log.
• state - The lifecycle state of the Fleet.
• system_tags - 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: {"orcl-cloud.free-tier-retained": "true"}
• time_created - The creation date and time of the Fleet (formatted according to RFC3339).