Skip to content
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.

Commit

Permalink
(maint) Route53 spec bug with zone ns record order
Browse files Browse the repository at this point in the history
 - AWS doesn't always return resource_records for ns in the same order
   in which they were set.  Fortunately, the type code compares array
   entries as sets already, so no module code needs to change.  The test
   has recently been observed as failing, however.
  • Loading branch information
Iristyle committed Mar 26, 2015
1 parent a632d43 commit fe03f4b
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion spec/acceptance/route53_spec.rb
Original file line number Diff line number Diff line change
Expand Up @@ -376,7 +376,7 @@ def find_record(name, zone, type)
r = PuppetManifest.new(@template, config).apply
expect(r[:output].any?{|x| x.include? 'Error'}).to eq(false)
record = find_record(config[:ns_record_name], @zone, 'NS')
expect(record.resource_records.map(&:values).flatten).to eq(config[:ns_values])
expect(record.resource_records.map(&:values).flatten.to_set).to eq(config[:ns_values].to_set)
end

end
Expand Down

0 comments on commit fe03f4b

Please sign in to comment.