Generates Agent Deploy Script for Fleet using the information provided.


oci jms fleet generate-agent-deploy-script [OPTIONS]

Required Parameters

--file [filename]

The name of the file that will receive the response data, or ‘-‘ to write to STDOUT.

--fleet-id [text]

The OCID of the Fleet.

--install-key-id [text]

The OCID of the install key for which to generate the script.

--is-user-name-enabled [boolean]

Enable/disable user name collection on agent.

--os-family [text]

The operating system type for the script. Currently only ‘LINUX’ and ‘WINDOWS’ are supported.

Accepted values are:


Optional Parameters

--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:

Example using required parameter

Copy and paste the following example into a JSON file, replacing the example parameters with your own.

    oci jms fleet create --generate-param-json-input inventory-log > inventory-log.json

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 compartment_id=<substitute-value-of-compartment_id> #
    export display_name=<substitute-value-of-display_name> #
    export install_key_id=<substitute-value-of-install_key_id> #
    export is_user_name_enabled=<substitute-value-of-is_user_name_enabled> #
    export os_family=<substitute-value-of-os_family> #

    fleet_id=$(oci jms fleet create --compartment-id $compartment_id --display-name $display_name --inventory-log file://inventory-log.json --query --raw-output)

    oci jms fleet generate-agent-deploy-script --file $file --fleet-id $fleet_id --install-key-id $install_key_id --is-user-name-enabled $is_user_name_enabled --os-family $os_family