cloudtools/stacker

AMI lookup should allow non-regex name filter to avoid slowness

Open

#555 opened on Mar 13, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (706 stars) (166 forks)batch import
enhancementgood first issuehelp wanted

Description

Looking up all Amazon-owned AMIs takes dozens of seconds for me. Even though I know the exact name of the AMI I want, the ami lookup still loads all of them and filters by regex. It should be possible to easily specify a non-regex filter that will passed-through to the API call directly.

Contributor guide

Tech stack
python
Domain
cloud
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonAWS EC2 API basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
Examine the current AMI lookup implementation in stacker, likely in the lookup module, to understand how it currently fetches AMIs and applies regex filtering. Consider adding a new parameter such as 'name exact' that uses the DescribeImages API with a filter by name for faster lookup. Check the AWS EC2 DescribeImages documentation for supported filters.
AMI lookup should allow non-regex name filter to avoid slowness · cloudtools/stacker#555 | Good First Issue