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

[TECH DEBT] The pillar configuration is confusing #30

Closed
lkubb opened this issue Dec 17, 2023 · 0 comments · Fixed by #29
Closed

[TECH DEBT] The pillar configuration is confusing #30

lkubb opened this issue Dec 17, 2023 · 0 comments · Fixed by #29

Comments

@lkubb
Copy link
Collaborator

lkubb commented Dec 17, 2023

Description of the tech debt to be addressed, include links and screenshots

For unclear reasons, the pillar module is currently confusingly configured like this:

- ext_pillar:
  - vault: path=foo/bar
  # or
  - vault:
      conf: path=foo/bar

It does not support multiple paths or any other configuration passed in the string.

It should be simplified to:

- ext_pillar:
  - vault: foo/bar
  # or
  - vault:
      path: foo/bar

Since we have the attention of people migrating explicitly anyways, let's do it in the initial release.

Versions Report

current main

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.

1 participant