Skip to content

Conversation

@ahgittin
Copy link
Contributor

Needed because our routines sometimes rewrite the plan

@ahgittin
Copy link
Contributor Author

Follow-up to #746 making it slightly more forgiving when replacing, should fix issues when dealing with complex catalogs/blueprints

@ahgittin ahgittin force-pushed the osgi-allow-equivalent-plans branch from 3f4188b to 56e3eec Compare July 21, 2017 13:00
Copy link
Contributor

@geomacy geomacy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM; will merge when test build succeeds

@geomacy
Copy link
Contributor

geomacy commented Jul 21, 2017

test failure is real, in CatalogResourceTest

@geomacy
Copy link
Contributor

geomacy commented Jul 21, 2017

It's just an update needed to the test expectations - there are now more tags than before on the result:

    "equivalent-plan(A8FA402166F072F19CFE88AEA200B001)",
    "equivalent-plan(A74550A5F94D4AD144AC5EB816DE6C45)",
    {
      "traits": [
        ...
      ]
    }

with test case that fails without the equivalent plan checks, but works with them
@ahgittin ahgittin force-pushed the osgi-allow-equivalent-plans branch from 56e3eec to bb9d1f8 Compare July 21, 2017 22:22
@ahgittin
Copy link
Contributor Author

thanks @geomacy - fixed and merged

@asfgit asfgit merged commit bb9d1f8 into apache:master Jul 21, 2017
asfgit pushed a commit that referenced this pull request Jul 21, 2017
Graeme-Miller pushed a commit to Graeme-Miller/brooklyn-server that referenced this pull request Aug 29, 2017
This reverts commit 9795c47, reversing
changes made to c694439.
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.

3 participants