describe-fleet-deployment¶
Description¶
Retrieves information about a managed container fleet deployment.
Request options
- Get information about the latest deployment for a specific fleet. Provide the fleet ID or ARN.
- Get information about a specific deployment. Provide the fleet ID or ARN and the deployment ID.
Results
If successful, a FleetDeployment object is returned.
See also: AWS API Documentation
Synopsis¶
describe-fleet-deployment
--fleet-id <value>
[--deployment-id <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
[--debug]
[--endpoint-url <value>]
[--no-verify-ssl]
[--no-paginate]
[--output <value>]
[--query <value>]
[--profile <value>]
[--region <value>]
[--version <value>]
[--color <value>]
[--no-sign-request]
[--ca-bundle <value>]
[--cli-read-timeout <value>]
[--cli-connect-timeout <value>]
[--cli-binary-format <value>]
[--no-cli-pager]
[--cli-auto-prompt]
[--no-cli-auto-prompt]
Options¶
--fleet-id (string)
A unique identifier for the container fleet. You can use either the fleet ID or ARN value.
--deployment-id (string)
A unique identifier for the deployment to return information for.
--cli-input-json | --cli-input-yaml (string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml.
--generate-cli-skeleton (string)
Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input, prints a sample input JSON that can be used as an argument for --cli-input-json. Similarly, if provided yaml-input it will print a sample input YAML that can be used with --cli-input-yaml. If provided with the value output, it validates the command inputs and returns a sample output JSON for that command. The generated JSON skeleton is not stable between versions of the AWS CLI and there are no backwards compatibility guarantees in the JSON skeleton generated.
Global Options¶
--debug (boolean)
Turn on debug logging.
--endpoint-url (string)
Override command’s default URL with the given URL.
--no-verify-ssl (boolean)
By default, the AWS CLI uses SSL when communicating with AWS services. For each SSL connection, the AWS CLI will verify SSL certificates. This option overrides the default behavior of verifying SSL certificates.
--no-paginate (boolean)
Disable automatic pagination. If automatic pagination is disabled, the AWS CLI will only make one call, for the first page of results.
--output (string)
The formatting style for command output.
- json
- text
- table
- yaml
- yaml-stream
--query (string)
A JMESPath query to use in filtering the response data.
--profile (string)
Use a specific profile from your credential file.
--region (string)
The region to use. Overrides config/env settings.
--version (string)
Display the version of this tool.
--color (string)
Turn on/off color output.
- on
- off
- auto
--no-sign-request (boolean)
Do not sign requests. Credentials will not be loaded if this argument is provided.
--ca-bundle (string)
The CA certificate bundle to use when verifying SSL certificates. Overrides config/env settings.
--cli-read-timeout (int)
The maximum socket read time in seconds. If the value is set to 0, the socket read will be blocking and not timeout. The default value is 60 seconds.
--cli-connect-timeout (int)
The maximum socket connect time in seconds. If the value is set to 0, the socket connect will be blocking and not timeout. The default value is 60 seconds.
--cli-binary-format (string)
The formatting style to be used for binary blobs. The default format is base64. The base64 format expects binary blobs to be provided as a base64 encoded string. The raw-in-base64-out format preserves compatibility with AWS CLI V1 behavior and binary values must be passed literally. When providing contents from a file that map to a binary blob fileb:// will always be treated as binary and use the file contents directly regardless of the cli-binary-format setting. When using file:// the file contents will need to properly formatted for the configured cli-binary-format.
- base64
- raw-in-base64-out
--no-cli-pager (boolean)
Disable cli pager for output.
--cli-auto-prompt (boolean)
Automatically prompt for CLI input parameters.
--no-cli-auto-prompt (boolean)
Disable automatically prompt for CLI input parameters.
Output¶
FleetDeployment -> (structure)
The requested deployment information.
DeploymentId -> (string)
A unique identifier for the deployment.FleetId -> (string)
A unique identifier for the container fleet.GameServerBinaryArn -> (string)
The unique identifier for the version of the game server container group definition that is being deployed.RollbackGameServerBinaryArn -> (string)
The unique identifier for the version of the game server container group definition to roll back to if deployment fails.PerInstanceBinaryArn -> (string)
The unique identifier for the version of the per-instance container group definition that is being deployed.RollbackPerInstanceBinaryArn -> (string)
The unique identifier for the version of the per-instance container group definition to roll back to if deployment fails.DeploymentStatus -> (string)
The status of fleet deployment activity in the location.
IN_PROGRESS– The deployment is in progress.IMPAIRED– The deployment failed and the fleet has some impaired containers.COMPLETE– The deployment has completed successfully.ROLLBACK_IN_PROGRESS– The deployment failed and rollback has been initiated.ROLLBACK_IN_COMPLETE– The deployment failed and rollback has been completed.CANCELLED– The deployment was cancelled.DeploymentConfiguration -> (structure)
Instructions for how to deploy updates to a container fleet and what actions to take if the deployment fails.
ProtectionStrategy -> (string)
Determines how fleet deployment activity affects active game sessions on the fleet. With protection, a deployment honors game session protection, and delays actions that would interrupt a protected active game session until the game session ends. Without protection, deployment activity can shut down all running tasks, including active game sessions, regardless of game session protection.MinimumHealthyPercentage -> (integer)
Sets a minimum level of healthy tasks to maintain during deployment activity.ImpairmentStrategy -> (string)
Determines what actions to take if a deployment fails. If the fleet is multi-location, this strategy applies across all fleet locations. With a rollback strategy, updated fleet instances are rolled back to the last successful deployment. Alternatively, you can maintain a few impaired containers for the purpose of debugging, while all other tasks return to the last successful deployment.CreationTime -> (timestamp)
A time stamp indicating when this data object was created. Format is a number expressed in Unix time as milliseconds (for example"1469498468.057").
LocationalDeployments -> (map)
If the deployment is for a multi-location fleet, the requests returns the deployment status in each fleet location.
key -> (string)
value -> (structure)
For a multi-location container fleet, describes the progress of a deployment across all fleet locations.
DeploymentStatus -> (string)
The status of fleet deployment activity in the location.
IN_PROGRESS– The deployment is in progress.IMPAIRED– The deployment failed and the fleet has some impaired containers.COMPLETE– The deployment has completed successfully.ROLLBACK_IN_PROGRESS– The deployment failed and rollback has been initiated.ROLLBACK_IN_COMPLETE– The deployment failed and rollback has been completed.CANCELLED– The deployment was cancelled.