运行aws ecs update-service --cluster cluster-name --service service-name --force-new-deployment --region ap-southeast-2将打开:
{
"service": {
"serviceArn": "arn:aws:ecs:ap-southeast-2:000000000000:service/service-name",
"serviceName": "service-name",
"clusterArn": "arn:aws:ecs:ap-southeast-2:000000000000:cluster/clustername",
"loadBalancers": [
{
"targetGroupArn": "arn:aws:elasticloadbalancing:ap-southeast-2:000000000000:targetgroup/targetgroupname",
"containerName": "containername",
"containerPort": 5000
}
],
"serviceRegistries": [],
"status": "ACTIVE",
"desiredCount": 1,
"runningCount": 1,
"pendingCount": 1,
"launchType": "FARGATE",
"platformVersion": "LATEST",
"taskDefinition": "arn:aws:ecs:ap-southeast-2:000000000000:task-definition/service-name:43",
:并阻止我的外壳,直到我按下q。这曾经工作得很好。我想我更新了我的AWSCLI,导致了这个问题。为什么会发生这种情况,我如何避免它来更新我的CI脚本中的服务?
发布于 2020-04-26 21:54:20
是的,这是AWS CLI2的默认行为。这应该可以解决你的问题(因为我不认为有一种内置的方法可以让它变得“安静”或安静)。
aws ecs update-service --service svcName --desired-count 1> /dev/null
除非万不得已,否则我不建议返回到较旧的版本。
发布于 2020-09-01 03:22:47
在找到AWS Documentation, How to use the AWS_PAGER environment variable之前,我遇到了这种行为,并尝试了许多方法来解决它
Windows:
C:\> setx AWS_PAGER ""Linux和MacOS:
export AWS_PAGER=""https://stackoverflow.com/questions/61440665
复制相似问题