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.

Sign up for GitHub

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

Jump to bottom

Add a concern for storing and accessing embedded ansible object ids #14377

Merged
merged 2 commits into from
Mar 20, 2017
Merged

Add a concern for storing and accessing embedded ansible object ids #14377

merged 2 commits into from
Mar 20, 2017

Commits on Mar 17, 2017

  1. Add a concern for storing and accessing default embedded ansible obje… 

    …ct ids

This will allow us to determine the ansible side object to relate
new objects to.

This also frees us from having to store an extra flag in our inventory
to identify which objects are the "system created" ones and which
are the other objects that may be artifacts of running jobs.

https://www.pivotaltracker.com/story/show/140098929
    @carbonin
    carbonin committed Mar 17, 2017
    Configuration menu
    Copy the full SHA
    5921219 View commit details
    Browse the repository at this point in the history

Commits on Mar 20, 2017

  1. Define the subject under test in provider specific spec files 

    This ensures that the specific provider under test implements
the defined behavior rather than just running the same set of
specs twice (what was being done with the shared subject).

Intorduced in eb6be29
    @carbonin
    carbonin committed Mar 20, 2017
    Configuration menu
    Copy the full SHA
    06a52e2 View commit details
    Browse the repository at this point in the history