15
51%

Ran 09 Aug 2016 12:39PM UTC

Jobs 1

Files 1

Run time 0s

Badge

Embed ▾

pending completion

Build # 15

Build Type

push

travis-ci

Committed by

michel-slm

Commit Message

Use `instance-state-name` instead of `instance-state-code`

When filtering for running instances, use `instance-state-name: running`
instead of `instance-state-code: 16`.

Per https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_InstanceState.html the state code is a two-byte number and the high byte could be anything.

That means that to use `instance-state-code` properly we have to either
filter for `instance-state-code` being any of 16, 16+256, 16+256*2, ...,
or do the filtering on the client side after retrieving all instances
matching the name tag.

Since that's inefficient, let's filter by `instance-state-name` instead.
That's more self-describing anyway.

Fixes #3.

and we don't want to grab all hosts and then filter by the masked val

Run Details

25 of 49 relevant lines covered (51.02%)

0.51 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
2	15.2	09 Aug 2016 12:39PM UTC	0	51.02	Travis Job 15.2

Source Files on build 15

Detailed source file information is not available for this build.

traveloka / ec2-route53-sync / 15
51%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 15

traveloka / ec2-route53-sync / 15 51%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 15

traveloka / ec2-route53-sync / 15
51%

README BADGES
x