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

feature request: eyaml checking #56

Closed
kjetilho opened this issue Jul 13, 2016 · 4 comments
Closed

feature request: eyaml checking #56

kjetilho opened this issue Jul 13, 2016 · 4 comments

Comments

@kjetilho
Copy link
Contributor

The default hieradata_path does not include *.eyaml. Although it is best practice to configure hiera-eyaml use .yaml as its file suffix, many will be using the default, .eyaml.

Ideally, it should also look for ENC[] values (in both .yaml and .eyaml, due to above mentioned BCP) and check that the content is valid BASE64.

@ghoneycutt
Copy link
Member

You should be able to check both with something like

 PuppetSyntax.hieradata_paths = ["**/*.yaml", "**/*.eyaml"]

@gdubicki
Copy link
Member

You can do with with a custom config, @ghoneycutt , but this should be a default as of now, when eyaml is a built-in backend in Hiera 5 (https://puppet.com/docs/puppet/5.3/hiera_migrate.html#updated-hiera-eyaml-users-go-for-it).

@gdubicki
Copy link
Member

Nvm, eyaml files ARE already checked by default since v. 2.3.0 (f65ed3a).

@bastelfreak
Copy link
Member

closed by #88

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.

4 participants