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.

Sign up for GitHub

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

Jump to bottom

incompatible changes in version 2.2.0 #161

Closed
vchepkov opened this issue Oct 12, 2016 · 4 comments
Closed

incompatible changes in version 2.2.0 #161

vchepkov opened this issue Oct 12, 2016 · 4 comments

Comments

@vchepkov
Copy link
Contributor

After upgrading module to version 2.2.0 order of the configured backends has changed

version 2.1.2:

:backends:
  - eyaml
  - yaml

version 2.2.0:

:backends:
- yaml
- eyaml

Also, notice lack of spaces before the array

Changing order of the backends can lead to unexpected results (as it was in my case)
@mmckinst
Copy link
Contributor

I've run in to the same issue. It can be worked around by specifying the order of the backends.

class { 'hiera':
  backends => [ 'eyaml', 'yaml' ],
}

mmckinst added a commit to mmckinst/puppet-hiera that referenced this issue Oct 13, 2016
@mmckinst
make eyaml be the first backend
d88096e 
older versions of this module had eyaml listed as the first
backend. people who use eyaml need eyaml as the first back end,
otherwise the encrypted valued will be read in as plan yaml and never
decrypted.

ref voxpupuli#161
mmckinst added a commit to mmckinst/puppet-hiera that referenced this issue Oct 13, 2016
@mmckinst
make eyaml be the first backend
d50a4e5 
older versions of this module had eyaml listed as the first
backend. people who use eyaml need eyaml as the first back end,
otherwise the encrypted valued will be read in as plain yaml and never
decrypted.

ref voxpupuli#161
@mmckinst mmckinst mentioned this issue Oct 13, 2016
Merged
@vchepkov
Copy link
Contributor Author

What about missing spaces? Patch doesn't seem to address that

@mmckinst
Copy link
Contributor

it will be parsed the same regardless of the spaces

@vchepkov
Copy link
Contributor Author

But it will cause unnecessary server restart as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vchepkov @mmckinst