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.

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

Resource registry_key { should_not exist } unavailable #322

Closed
larryebaum opened this issue Dec 15, 2015 · 2 comments
Closed

Resource registry_key { should_not exist } unavailable #322

larryebaum opened this issue Dec 15, 2015 · 2 comments
Assignees
Labels
Type: Bug Feature not working as expected
Milestone

Comments

@larryebaum
Copy link
Contributor

The following code fails as it isn't supported; it is necessary as in many cases we want to ensure that either a key doesn't exist but in the case that if it does, that it matches a particular value. The former isn't possible whereas the latter is.

describe registry_key('path\to\key') do
  it { should_not exist }
end
@larryebaum larryebaum added the Type: Bug Feature not working as expected label Dec 15, 2015
@chris-rock
Copy link
Contributor

We should have an integration test for this bug as well. Thanks @larryebaum for reporting this.

@chris-rock chris-rock self-assigned this Dec 30, 2015
@chris-rock chris-rock added this to the 0.9.9 milestone Dec 30, 2015
@chris-rock
Copy link
Contributor

solved with #364 please reopen if this stays a problem after this release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Feature not working as expected
Projects
None yet
Development

No branches or pull requests

2 participants