Skip to content

Conversation

adrienthebo
Copy link

This supersedes #657

When testing a resolution, the confines may be tested to confirm
suitability on a given platform and so may be changed without destroying
and recreating the resolution. Because of this we need to recalculate
suitability every time #suitable? method is invoked. In normal operation
fact suitability is only determined once so this should have no
performance impact.
The existing EC2 API implemented all methods on a module object, which
made for a rather clumsy API that required intrusive stubbing to test.
This commit implements a new object based API that should be cleaner to
use.
With commit 5ca456f we have a new method of querying the EC2 API; the
old methods can be deprecated.
@puppetcla
Copy link

CLA signed by all contributors.

kylog pushed a commit that referenced this pull request Apr 16, 2014
…ructured-ec2-metadata

Feature/facter 2/fact 185 structured ec2 metadata
@kylog kylog merged commit e3da030 into puppetlabs:stable Apr 16, 2014
@adrienthebo adrienthebo deleted the feature/facter-2/fact-185-structured-ec2-metadata branch April 21, 2014 22:19
kylog pushed a commit that referenced this pull request May 23, 2014
…t-185-structured-ec2-metadata"

This reverts commit e3da030, reversing
changes made to 2ce8849.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants