mirror of
https://github.com/kubernetes-sigs/kustomize.git
synced 2026-07-01 18:30:15 +00:00
change github.com/aws/aws-sdk-go to be the same revision in kubernetes
This commit is contained in:
Jingfang Liu
1
vendor/github.com/aws/aws-sdk-go/models/apis/elasticmapreduce/2009-03-31/api-2.json
generated
vendored
1
vendor/github.com/aws/aws-sdk-go/models/apis/elasticmapreduce/2009-03-31/api-2.json
generated
vendored
@@ -7,7 +7,6 @@
|
||||
"protocol":"json",
|
||||
"serviceAbbreviation":"Amazon EMR",
|
||||
"serviceFullName":"Amazon Elastic MapReduce",
|
||||
"serviceId":"EMR",
|
||||
"signatureVersion":"v4",
|
||||
"targetPrefix":"ElasticMapReduce",
|
||||
"timestampFormat":"unixTimestamp",
|
||||
|
||||
18
vendor/github.com/aws/aws-sdk-go/models/apis/elasticmapreduce/2009-03-31/docs-2.json
generated
vendored
18
vendor/github.com/aws/aws-sdk-go/models/apis/elasticmapreduce/2009-03-31/docs-2.json
generated
vendored
@@ -9,7 +9,7 @@
|
||||
"CancelSteps": "<p>Cancels a pending step or steps in a running cluster. Available only in Amazon EMR versions 4.8.0 and later, excluding version 5.0.0. A maximum of 256 steps are allowed in each CancelSteps request. CancelSteps is idempotent but asynchronous; it does not guarantee a step will be canceled, even if the request is successfully submitted. You can only cancel steps that are in a <code>PENDING</code> state.</p>",
|
||||
"CreateSecurityConfiguration": "<p>Creates a security configuration, which is stored in the service and can be specified when a cluster is created.</p>",
|
||||
"DeleteSecurityConfiguration": "<p>Deletes a security configuration.</p>",
|
||||
"DescribeCluster": "<p>Provides cluster-level details including status, hardware and software configuration, VPC settings, and so on. </p>",
|
||||
"DescribeCluster": "<p>Provides cluster-level details including status, hardware and software configuration, VPC settings, and so on. For information about the cluster steps, see <a>ListSteps</a>.</p>",
|
||||
"DescribeJobFlows": "<p>This API is deprecated and will eventually be removed. We recommend you use <a>ListClusters</a>, <a>DescribeCluster</a>, <a>ListSteps</a>, <a>ListInstanceGroups</a> and <a>ListBootstrapActions</a> instead.</p> <p>DescribeJobFlows returns a list of job flows that match all of the supplied parameters. The parameters can include a list of job flow IDs, job flow states, and restrictions on job flow creation date and time.</p> <p>Regardless of supplied parameters, only job flows created within the last two months are returned.</p> <p>If no parameters are supplied, then job flows matching either of the following criteria are returned:</p> <ul> <li> <p>Job flows created and completed in the last two weeks</p> </li> <li> <p> Job flows created within the last two months that are in one of the following states: <code>RUNNING</code>, <code>WAITING</code>, <code>SHUTTING_DOWN</code>, <code>STARTING</code> </p> </li> </ul> <p>Amazon EMR can return a maximum of 512 job flow descriptions.</p>",
|
||||
"DescribeSecurityConfiguration": "<p>Provides the details of a security configuration by returning the configuration JSON.</p>",
|
||||
"DescribeStep": "<p>Provides more detail about the cluster step.</p>",
|
||||
@@ -1365,7 +1365,7 @@
|
||||
"Cluster$LogUri": "<p>The path to the Amazon S3 location where logs for this cluster are stored.</p>",
|
||||
"Cluster$RequestedAmiVersion": "<p>The AMI version requested for this cluster.</p>",
|
||||
"Cluster$RunningAmiVersion": "<p>The AMI version running on this cluster.</p>",
|
||||
"Cluster$ReleaseLabel": "<p>The Amazon EMR release label, which determines the version of open-source application packages installed on the cluster. Release labels are in the form <code>emr-x.x.x</code>, where x.x.x is an Amazon EMR release version, for example, <code>emr-5.14.0</code>. For more information about Amazon EMR release versions and included application versions and features, see <a href=\"http://docs.aws.amazon.com/emr/latest/ReleaseGuide/\">http://docs.aws.amazon.com/emr/latest/ReleaseGuide/</a>. The release label applies only to Amazon EMR releases versions 4.x and later. Earlier versions use <code>AmiVersion</code>.</p>",
|
||||
"Cluster$ReleaseLabel": "<p>The release label for the Amazon EMR release.</p>",
|
||||
"Cluster$ServiceRole": "<p>The IAM role that will be assumed by the Amazon EMR service to access AWS resources on your behalf.</p>",
|
||||
"Cluster$MasterPublicDnsName": "<p>The DNS name of the master node. If the cluster is on a private subnet, this is the private DNS name. On a public subnet, this is the public DNS name.</p>",
|
||||
"ClusterStateChangeReason$Message": "<p>The descriptive message for the state change reason.</p>",
|
||||
@@ -1397,7 +1397,7 @@
|
||||
"Instance$InstanceGroupId": "<p>The identifier of the instance group to which this instance belongs.</p>",
|
||||
"InstanceFleetStateChangeReason$Message": "<p>An explanatory message.</p>",
|
||||
"InstanceGroup$Name": "<p>The name of the instance group.</p>",
|
||||
"InstanceGroup$BidPrice": "<p>The maximum Spot price your are willing to pay for EC2 instances.</p> <p>An optional, nullable field that applies if the <code>MarketType</code> for the instance group is specified as <code>SPOT</code>. Specify the maximum spot price in USD. If the value is NULL and <code>SPOT</code> is specified, the maximum Spot price is set equal to the On-Demand price.</p>",
|
||||
"InstanceGroup$BidPrice": "<p>The bid price for each EC2 instance in the instance group when launching nodes as Spot Instances, expressed in USD.</p>",
|
||||
"InstanceGroupStateChangeReason$Message": "<p>The status change reason description.</p>",
|
||||
"InstanceStateChangeReason$Message": "<p>The status change reason description.</p>",
|
||||
"MetricDimension$Key": "<p>The dimension name.</p>",
|
||||
@@ -1558,19 +1558,19 @@
|
||||
"InstanceFleet$Name": "<p>A friendly name for the instance fleet.</p>",
|
||||
"InstanceFleetConfig$Name": "<p>The friendly name of the instance fleet.</p>",
|
||||
"InstanceGroupConfig$Name": "<p>Friendly name given to the instance group.</p>",
|
||||
"InstanceGroupConfig$BidPrice": "<p>The maximum Spot price your are willing to pay for EC2 instances.</p> <p>An optional, nullable field that applies if the <code>MarketType</code> for the instance group is specified as <code>SPOT</code>. Specify the maximum spot price in USD. If the value is NULL and <code>SPOT</code> is specified, the maximum Spot price is set equal to the On-Demand price.</p>",
|
||||
"InstanceGroupConfig$BidPrice": "<p>Bid price for each EC2 instance in the instance group when launching nodes as Spot Instances, expressed in USD.</p>",
|
||||
"InstanceGroupDetail$InstanceGroupId": "<p>Unique identifier for the instance group.</p>",
|
||||
"InstanceGroupDetail$Name": "<p>Friendly name for the instance group.</p>",
|
||||
"InstanceGroupDetail$BidPrice": "<p>The maximum Spot price your are willing to pay for EC2 instances.</p> <p>An optional, nullable field that applies if the <code>MarketType</code> for the instance group is specified as <code>SPOT</code>. Specified in USD. If the value is NULL and <code>SPOT</code> is specified, the maximum Spot price is set equal to the On-Demand price.</p>",
|
||||
"InstanceGroupDetail$BidPrice": "<p>Bid price for EC2 Instances when launching nodes as Spot Instances, expressed in USD.</p>",
|
||||
"InstanceGroupIdsList$member": null,
|
||||
"InstanceGroupModifyConfig$InstanceGroupId": "<p>Unique ID of the instance group to expand or shrink.</p>",
|
||||
"InstanceTypeConfig$BidPrice": "<p>The bid price for each EC2 Spot instance type as defined by <code>InstanceType</code>. Expressed in USD. If neither <code>BidPrice</code> nor <code>BidPriceAsPercentageOfOnDemandPrice</code> is provided, <code>BidPriceAsPercentageOfOnDemandPrice</code> defaults to 100%. </p>",
|
||||
"InstanceTypeSpecification$BidPrice": "<p>The bid price for each EC2 Spot instance type as defined by <code>InstanceType</code>. Expressed in USD.</p>",
|
||||
"JobFlowDetail$JobFlowId": "<p>The job flow identifier.</p>",
|
||||
"JobFlowDetail$Name": "<p>The name of the job flow.</p>",
|
||||
"JobFlowDetail$AmiVersion": "<p>Applies only to Amazon EMR AMI versions 3.x and 2.x. For Amazon EMR releases 4.0 and later, <code>ReleaseLabel</code> is used. To specify a custom AMI, use <code>CustomAmiID</code>.</p>",
|
||||
"JobFlowDetail$AmiVersion": "<p>Used only for version 2.x and 3.x of Amazon EMR. The version of the AMI used to initialize Amazon EC2 instances in the job flow. For a list of AMI versions supported by Amazon EMR, see <a href=\"http://docs.aws.amazon.com/emr/latest/DeveloperGuide/emr-dg.pdf#nameddest=ami-versions-supported\">AMI Versions Supported in EMR</a> in the <i>Amazon EMR Developer Guide.</i> </p>",
|
||||
"JobFlowInstancesConfig$Ec2KeyName": "<p>The name of the EC2 key pair that can be used to ssh to the master node as the user called \"hadoop.\"</p>",
|
||||
"JobFlowInstancesConfig$HadoopVersion": "<p>Applies only to Amazon EMR release versions earlier than 4.0. The Hadoop version for the cluster. Valid inputs are \"0.18\" (deprecated), \"0.20\" (deprecated), \"0.20.205\" (deprecated), \"1.0.3\", \"2.2.0\", or \"2.4.0\". If you do not set this value, the default of 0.18 is used, unless the <code>AmiVersion</code> parameter is set in the RunJobFlow call, in which case the default version of Hadoop for that AMI version is used.</p>",
|
||||
"JobFlowInstancesConfig$HadoopVersion": "<p>The Hadoop version for the cluster. Valid inputs are \"0.18\" (deprecated), \"0.20\" (deprecated), \"0.20.205\" (deprecated), \"1.0.3\", \"2.2.0\", or \"2.4.0\". If you do not set this value, the default of 0.18 is used, unless the AmiVersion parameter is set in the RunJobFlow call, in which case the default version of Hadoop for that AMI version is used.</p>",
|
||||
"JobFlowInstancesConfig$Ec2SubnetId": "<p>Applies to clusters that use the uniform instance group configuration. To launch the cluster in Amazon Virtual Private Cloud (Amazon VPC), set this parameter to the identifier of the Amazon VPC subnet where you want the cluster to launch. If you do not specify this value, the cluster launches in the normal Amazon Web Services cloud, outside of an Amazon VPC, if the account launching the cluster supports EC2 Classic networks in the region where the cluster launches.</p> <p>Amazon VPC currently does not support cluster compute quadruple extra large (cc1.4xlarge) instances. Thus you cannot specify the cc1.4xlarge instance type for clusters launched in an Amazon VPC.</p>",
|
||||
"JobFlowInstancesConfig$EmrManagedMasterSecurityGroup": "<p>The identifier of the Amazon EC2 security group for the master node.</p>",
|
||||
"JobFlowInstancesConfig$EmrManagedSlaveSecurityGroup": "<p>The identifier of the Amazon EC2 security group for the slave nodes.</p>",
|
||||
@@ -1584,8 +1584,8 @@
|
||||
"KerberosAttributes$ADDomainJoinUser": "<p>Required only when establishing a cross-realm trust with an Active Directory domain. A user with sufficient privileges to join resources to the domain.</p>",
|
||||
"KerberosAttributes$ADDomainJoinPassword": "<p>The Active Directory password for <code>ADDomainJoinUser</code>.</p>",
|
||||
"RunJobFlowInput$Name": "<p>The name of the job flow.</p>",
|
||||
"RunJobFlowInput$AmiVersion": "<p>Applies only to Amazon EMR AMI versions 3.x and 2.x. For Amazon EMR releases 4.0 and later, <code>ReleaseLabel</code> is used. To specify a custom AMI, use <code>CustomAmiID</code>.</p>",
|
||||
"RunJobFlowInput$ReleaseLabel": "<p>The Amazon EMR release label, which determines the version of open-source application packages installed on the cluster. Release labels are in the form <code>emr-x.x.x</code>, where x.x.x is an Amazon EMR release version, for example, <code>emr-5.14.0</code>. For more information about Amazon EMR release versions and included application versions and features, see <a href=\"http://docs.aws.amazon.com/emr/latest/ReleaseGuide/\">http://docs.aws.amazon.com/emr/latest/ReleaseGuide/</a>. The release label applies only to Amazon EMR releases versions 4.x and later. Earlier versions use <code>AmiVersion</code>.</p>",
|
||||
"RunJobFlowInput$AmiVersion": "<p>For Amazon EMR AMI versions 3.x and 2.x. For Amazon EMR releases 4.0 and later, the Linux AMI is determined by the <code>ReleaseLabel</code> specified or by <code>CustomAmiID</code>. The version of the Amazon Machine Image (AMI) to use when launching Amazon EC2 instances in the job flow. For details about the AMI versions currently supported in EMR version 3.x and 2.x, see <a href=\"emr/latest/DeveloperGuide/emr-dg.pdf#nameddest=ami-versions-supported\">AMI Versions Supported in EMR</a> in the <i>Amazon EMR Developer Guide</i>. </p> <p>If the AMI supports multiple versions of Hadoop (for example, AMI 1.0 supports both Hadoop 0.18 and 0.20), you can use the <a>JobFlowInstancesConfig</a> <code>HadoopVersion</code> parameter to modify the version of Hadoop from the defaults shown above.</p> <note> <p>Previously, the EMR AMI version API parameter options allowed you to use latest for the latest AMI version rather than specify a numerical value. Some regions no longer support this deprecated option as they only have a newer release label version of EMR, which requires you to specify an EMR release label release (EMR 4.x or later).</p> </note>",
|
||||
"RunJobFlowInput$ReleaseLabel": "<p> The release label for the Amazon EMR release. For Amazon EMR 3.x and 2.x AMIs, use <code>AmiVersion</code> instead.</p>",
|
||||
"RunJobFlowInput$CustomAmiId": "<p>Available only in Amazon EMR version 5.7.0 and later. The ID of a custom Amazon EBS-backed Linux AMI. If specified, Amazon EMR uses this AMI when it launches cluster EC2 instances. For more information about custom AMIs in Amazon EMR, see <a href=\"http://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-custom-ami.html\">Using a Custom AMI</a> in the <i>Amazon EMR Management Guide</i>. If omitted, the cluster uses the base Linux AMI for the <code>ReleaseLabel</code> specified. For Amazon EMR versions 2.x and 3.x, use <code>AmiVersion</code> instead.</p> <p>For information about creating a custom AMI, see <a href=\"http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html\">Creating an Amazon EBS-Backed Linux AMI</a> in the <i>Amazon Elastic Compute Cloud User Guide for Linux Instances</i>. For information about finding an AMI ID, see <a href=\"http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/finding-an-ami.html\">Finding a Linux AMI</a>. </p>",
|
||||
"RunJobFlowOutput$JobFlowId": "<p>An unique identifier for the job flow.</p>",
|
||||
"SecurityGroupsList$member": null,
|
||||
|
||||
18
vendor/github.com/aws/aws-sdk-go/models/apis/elasticmapreduce/2009-03-31/smoke.json
generated
vendored
18
vendor/github.com/aws/aws-sdk-go/models/apis/elasticmapreduce/2009-03-31/smoke.json
generated
vendored
@@ -1,18 +0,0 @@
|
||||
{
|
||||
"version": 1,
|
||||
"defaultRegion": "us-west-2",
|
||||
"testCases": [
|
||||
{
|
||||
"operationName": "ListClusters",
|
||||
"input": {},
|
||||
"errorExpectedFromService": false
|
||||
},
|
||||
{
|
||||
"operationName": "DescribeCluster",
|
||||
"input": {
|
||||
"ClusterId": "fake_cluster"
|
||||
},
|
||||
"errorExpectedFromService": true
|
||||
}
|
||||
]
|
||||
}
|
||||
Reference in New Issue
Block a user