Permalink
Commits on Nov 3, 2010
  1. @danielsdeleo

    make context explicit in specs so they run correctly in any order

    and also fix a bug in shell out's environment variable setting
    danielsdeleo committed Nov 3, 2010
  2. @danielsdeleo
  3. @danielsdeleo
Commits on Nov 2, 2010
  1. @seth

    Merge branch 'environments'

    Conflicts:
    	features/api/roles/list_roles_api.feature
    seth committed Nov 2, 2010
  2. @algorist
  3. @algorist
  4. @algorist
  5. @algorist
  6. @algorist
  7. @algorist
  8. @algorist

    Deleting a test whose pre-condition (no clients have been created) ca…

    …nnot be met due to test harness pre-test client creation
    algorist committed Nov 2, 2010
  9. @algorist
  10. @seth
  11. @seth

    Make the test for respecting cookbook version dependencies pending

    The functionality being tested is not yet available.
    seth committed Nov 2, 2010
  12. @seth

    Use Chef::Version instead of Gem::Version in nodes controller CHEF-1818

    Also fix cookbook version handling in nodes controller
    
    This was broken, probably from some merge work that didn't get
    tested.  Respecting versions in dependencies still not wired up.
    seth committed Oct 29, 2010
  13. @seth
  14. @seth
  15. @seth
  16. @seth
  17. @seth
  18. @seth

    Allow only one version constraint in metadata CHEF-1818

    This change is NOT backwards compatible.  However, since version
    contraints have not yet been actionable, they have not likely seen
    extensive use.
    
    The following DSL functions used to accept a variable number of
    version constraints.  They now accept only a single constraint:
    
        supports, depends, recommends, suggests, conflicts, provides,
        replaces
    
    Furthermore, we no longer support Debian-style constraints.  Instead
    of '>>' and '<<', use '>' and '<'.
    seth committed Oct 28, 2010
  19. @seth

    Add VersionConstraint class CHEF-1818

    This will help us enforce version constraints in cookbook metadata
    (depends, conflicts) as well as for the allowed cookbook versions in
    environments.
    
    Any saved metadata with no version specified for a dependency will
    have a JSON value of [].  This patch avoids users having to reload
    such cookbooks.  CHEF-1818
    seth committed Oct 27, 2010
  20. @seth
  21. @seth

    Extract Metadata::Version as Chef::Version CHEF-1818

    Chef::Version, which lives in version_class.rb, replaces
    Metadata::Version
    
    This is used in CookbookVersion and will be used for implementing
    version contraints for cookbook metadata and environments.
    seth committed Oct 27, 2010
  22. @seth
Commits on Nov 1, 2010
  1. @seth

    correct knife environment edit spec

    Nuo Yan committed with seth Oct 12, 2010
  2. @seth

    bump the version to 0.10.0.beta.0

    Nuo Yan committed with seth Oct 12, 2010
  3. @seth

    update test fixtures for the per environment run list data structure …

    …change
    Nuo Yan committed with seth Oct 8, 2010
  4. @seth

    revise per environment data structure

    Nuo Yan committed with seth Oct 7, 2010
  5. @seth

    enable search for environment objects and complete the knife environm…

    …ent from file feature
    Nuo Yan committed with seth Sep 23, 2010
  6. @seth

    not loading environment object in node's expand! method if the enviro…

    …nment is _default
    Nuo Yan committed with seth Sep 20, 2010
  7. @seth

    adding attributes to the environment object

    Nuo Yan committed with seth Sep 20, 2010
  8. @seth

    run chef-client in the environment if the user specifies :environment…

    … in the client.rb file
    Nuo Yan committed with seth Sep 16, 2010
  9. @seth

    more fixes and improvements for environments

    Nuo Yan committed with seth Sep 14, 2010
  10. @sdelano @seth