-
Notifications
You must be signed in to change notification settings - Fork 59
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
feat: allow install_from_repo #59
base: master
Are you sure you want to change the base?
Conversation
75eafc1
to
07a25b9
Compare
Any hint on how to write specific tests for those? |
Hi, thanks for your contribution. Let me take a couple of days to take a look at this. |
@dafyddj had you any time in the last months? |
Hi, sorry for the long delay. Can you rebase this PR and push to re-run the tests? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please observe the formatting required for commit messages.
Something like feat(repo): ...
pillar.example
Outdated
install_from_repo: False # Set to True to install package rather than extract archive | ||
repo: ... # Might specify a specific repo, if not present in map | ||
package: vault # If package would have any other name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please observe the yaml formatting problems covered by pre-commit
.
The pillar values are self-explanatory, so do not require commenting but please supply an actual example value for repo
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated.
vault/osfamilymap.yaml
Outdated
repo_key: "https://apt.releases.hashicorp.com/gpg" | ||
repo_configfile: '/etc/vault.d/vault.hcl' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quotes not required here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed
vault/osfamilymap.yaml
Outdated
@@ -3,6 +3,9 @@ | |||
--- | |||
Debian: | |||
setcap_pkg: libcap2-bin | |||
repo: "deb [arch={{ grains['osarch'] }}] https://apt.releases.hashicorp.com {{ grains['oscodename'] }} main" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please split long lines.
repo: "deb [arch={{ grains['osarch'] }}] https://apt.releases.hashicorp.com {{ grains['oscodename'] }} main" | |
repo: 'deb [arch={{ grains['osarch'] }}] https://apt.releases.hashicorp.com | |
{{ grains['oscodename'] }} main' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed. Along other stuffs, to get CI ok.
734644a
to
8653424
Compare
Allow install via package from a repository
Is there a status update on this? |
Vault debian repo added as an option
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
Related to #53
Describe the changes you're proposing
Support install from (hashicorp) repo - with proper defaults for Debian
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context