Retrieve a list of module stream profiles, along with a summary of their of their status, from a managed instance. Filters may be applied to select a subset of profiles based on the filter criteria.

The “moduleName”, “streamName”, and “profileName” attributes combine to form a set of filters on the list of module stream profiles. If a “modulName” is provided, only profiles that belong to that module are returned. If both a “moduleName” and “streamName” are given, only profiles belonging to that module stream are returned. Finally, if all three are given then only the particular profile indicated by the triple is returned. It is not valid to supply a “streamName” without a “moduleName”. It is also not valid to supply a “profileName” without a “streamName”.

The “status” attribute filters against the state of a module stream profile. Valid values are “INSTALLED” and “AVAILABLE”. If the attribute is set to “INSTALLED”, only module stream profiles that are installed are included in the result set. If the attribute is set to “AVAILABLE”, only module stream profiles that are not installed are included in the result set. If the attribute is not defined, the request is not subject to this filter.

When sorting by display name, the result set is sorted first by module name, then by stream name, and finally by profile name.


oci os-management managed-instance list-module-profiles [OPTIONS]

Required Parameters

--managed-instance-id [text]

OCID for the managed instance

Optional Parameters


Fetches all pages of results. If you provide this option, then you cannot provide the --limit option.

--compartment-id, -c [text]

The ID of the compartment in which to list resources. This parameter is optional and in some cases may have no effect.

--from-json [text]

Provide input to this command as a JSON document from a file using the file://path-to/file syntax.

The --generate-full-command-json-input option can be used to generate a sample json file to be used with this command option. The key names are pre-populated and match the command option names (converted to camelCase format, e.g. compartment-id –> compartmentId), while the values of the keys need to be populated by the user before using the sample file as an input to this command. For any command option that accepts multiple values, the value of the key can be a JSON array.

Options can still be provided on the command line. If an option exists in both the JSON document and the command line then the command line specified value will be used.

For examples on usage of this option, please see our “using CLI with advanced JSON options” link:

--limit [integer]

The maximum number of items to return.

--max-wait-seconds [integer]

The maximum time to wait for the work request to reach the state defined by --wait-for-state. Defaults to 1200 seconds.

--module-name [text]

The name of a module. This parameter is required if a streamName is specified.

--page [text]

The page token representing the page at which to start retrieving results. This is usually retrieved from a previous list call.

--page-size [integer]

When fetching results, the number of results to fetch per call. Only valid when used with --all or --limit, and ignored otherwise.

--profile-name [text]

The name of the profile of the containing module stream

--profile-status [text]

The status of the profile.

A profile with the “INSTALLED” status indicates that the profile has been installed.

A profile with the “AVAILABLE” status indicates that the profile is not installed, but can be.

Accepted values are:

--sort-by [text]

The field to sort by. Only one sort order may be provided. Default order for TIMECREATED is descending. Default order for DISPLAYNAME is ascending. If no value is specified TIMECREATED is default.

Accepted values are:

--sort-order [text]

The sort order to use, either ‘asc’ or ‘desc’.

Accepted values are:

--stream-name [text]

The name of the stream of the containing module. This parameter is required if a profileName is specified.

--wait-for-state [text]

This operation asynchronously creates, modifies or deletes a resource and uses a work request to track the progress of the operation. Specify this option to perform the action and then wait until the work request reaches a certain state. Multiple states can be specified, returning on the first state. For example, --wait-for-state SUCCEEDED --wait-for-state FAILED would return on whichever lifecycle state is reached first. If timeout is reached, a return code of 2 is returned. For any other error, a return code of 1 is returned.

Accepted values are:

--wait-interval-seconds [integer]

Check every --wait-interval-seconds to see whether the work request has reached the state defined by --wait-for-state. Defaults to 30 seconds.

Example using required parameter

Copy the following CLI commands into a file named Run the command by typing “bash” and replacing the example parameters with your own.

Please note this sample will only work in the POSIX-compliant bash-like shell. You need to set up the OCI configuration and appropriate security policies before trying the examples.

    export managed_instance_id=<substitute-value-of-managed_instance_id> #

    oci os-management managed-instance list-module-profiles --managed-instance-id $managed_instance_id