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

According to README, default value for manifest option is nil #292

Closed
neomilium opened this issue Nov 18, 2020 · 6 comments
Closed

According to README, default value for manifest option is nil #292

neomilium opened this issue Nov 18, 2020 · 6 comments

Comments

@neomilium
Copy link
Contributor

Since 3.9.0, manifest option is set to 'manifests/` directory which is different from README instructions.

Reading git logs, we could see:

If, for some reason, you want onceover to avoid compiling your environment's site manifests, set :manifest to a non-existent path

IMHO, using a non-existent path is not relevant.

@smortex
Copy link
Member

smortex commented Nov 18, 2020

IMHO, using a non-existent path is not relevant.

Yes it's weird 😦.

I am still not sure about the best way to fix it. A quick fix for me was to set it to manifests/site.pp (which exist) but move the default node configuration in a separate file (i.e. site/default.pp), so that onceover only catch the default values set in site.pp but since Puppet concatenate all stanzas from files in the site directory, the behavior does not change when applying catalogs. But this is annoying because by convention I expect manifests/site.pp to both include the default node and the default settings.

@smortex
Copy link
Member

smortex commented Nov 18, 2020

In a way, the new behavior of taking manifests/* into account seems fine-ish, but this deserve a major version bump I think since after update, onceover acts differently and does not test the same thing as before…

Ignoring node default { ... } from these files would probably help avoiding this and still make sense since the goal of onceover is to harness test roles & profiles?

@neomilium
Copy link
Contributor Author

In a way, the new behavior of taking manifests/* into account seems fine-ish, but this deserve a major version bump I think since after update, onceover acts differently and does not test the same thing as before…

3.9.0 version already acts differently as before… this patch allow to back to normal.

@neomilium
Copy link
Contributor Author

neomilium commented Nov 18, 2020

Ignoring node default { ... } from these files would probably help avoiding this and still make sense since the goal of onceover is to harness test roles & profiles?

Ignoring node default { ... } could be a solution but onceover did not handle manifest/ internally and rely on rspec-puppet to do it: https://github.com/dylanratcliffe/onceover/blob/master/templates/spec_helper.rb.erb#L32

@neomilium
Copy link
Contributor Author

Need to verify this but with this patch, it allow to set manifest per class_groups.
This way you can test roles and profiles without manifest/ and test other things with it.

@dylanratcliffe
Copy link
Collaborator

Fixed in 3.19.1

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 a pull request may close this issue.

3 participants