Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(provider/ecs): fetch all images for ECR repos with >100 images #2948

Merged
merged 4 commits into from
Sep 18, 2018
Merged

fix(provider/ecs): fetch all images for ECR repos with >100 images #2948

merged 4 commits into from
Sep 18, 2018

Conversation

fcoelho
Copy link
Contributor

@fcoelho fcoelho commented Sep 7, 2018

ECR repositories may contain many images, but the ListImages
operation will retrieve at most 100 at a time [1]. For repositories with
more than 100 images this used to cause pipelines depending on that
repository to randomly fail when you start getting over the limit (as
the desired image would not be on the first page of results).

This commit builds upon the ListImages operation and the nextToken
value to fetch all images available in the repository. And only images
matching the desired tag/digest will be sent to DescribeImages.

Some tests were slightly modified to include an empty list instead of
null in the imageIds field as:

  1. that's what the ListImages returns in case there are no images in the repository
  2. the code now uses the results from the ListImages operation to filter the images instead of the results of DescribeImages as previously done

[1]: https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/ecr/model/ListImagesRequest.html#getMaxResults--

fcoelho and others added 2 commits September 7, 2018 19:20
ECR repositories may contain many images, but the `ListImages`
operation will retrieve at most 100 at a time [1]. For repositories with
more than 100 images this used to cause pipelines depending on that
repository to randomly fail when you start getting over the limit (as
the desired image would not be on the first page of results).

This commit builds upon the `ListImages` operation and the `nextToken`
value to fetch all images available in the repository. And only images
matching the desired tag/digest are sent to `DescribeImages`.

Some tests were slightly modified to include an empty list instead of
`null` in the `imageIds` field as:

1. that's what the `ListImages` returns in case there are no images in
   the repository
2. the code now uses the results from the `ListImages` operation to
   filter the images instead of the results of `DescribeImages` as
   previously done

[1]: https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/ecr/model/ListImagesRequest.html#getMaxResults--
@tomaslin
Copy link
Contributor

@clareliguori @BrunoCarrier can either of you LGTM this PR?

Copy link
Member

@clareliguori clareliguori left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tomaslin tomaslin merged commit 16d4f17 into spinnaker:master Sep 18, 2018
radubutnaru pushed a commit to radubutnaru/clouddriver that referenced this pull request Sep 19, 2018
…pinnaker#2948)

ECR repositories may contain many images, but the `ListImages`
operation will retrieve at most 100 at a time [1]. For repositories with
more than 100 images this used to cause pipelines depending on that
repository to randomly fail when you start getting over the limit (as
the desired image would not be on the first page of results).

This commit builds upon the `ListImages` operation and the `nextToken`
value to fetch all images available in the repository. And only images
matching the desired tag/digest are sent to `DescribeImages`.

Some tests were slightly modified to include an empty list instead of
`null` in the `imageIds` field as:

1. that's what the `ListImages` returns in case there are no images in
   the repository
2. the code now uses the results from the `ListImages` operation to
   filter the images instead of the results of `DescribeImages` as
   previously done

[1]: https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/ecr/model/ListImagesRequest.html#getMaxResults--
clanesf pushed a commit to clanesf/clouddriver that referenced this pull request Dec 8, 2018
…pinnaker#2948)

ECR repositories may contain many images, but the `ListImages`
operation will retrieve at most 100 at a time [1]. For repositories with
more than 100 images this used to cause pipelines depending on that
repository to randomly fail when you start getting over the limit (as
the desired image would not be on the first page of results).

This commit builds upon the `ListImages` operation and the `nextToken`
value to fetch all images available in the repository. And only images
matching the desired tag/digest are sent to `DescribeImages`.

Some tests were slightly modified to include an empty list instead of
`null` in the `imageIds` field as:

1. that's what the `ListImages` returns in case there are no images in
   the repository
2. the code now uses the results from the `ListImages` operation to
   filter the images instead of the results of `DescribeImages` as
   previously done

[1]: https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/ecr/model/ListImagesRequest.html#getMaxResults--
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants