This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR upgrades the SDK to use Guzzle 6.
I am still exercising these changes with functionality very similar to the examples (
shell.php
andtask.php
), hence the "hold" designation for now.I am curious how others are using this SDK now or would like to in the future.
My initial use case is seeding vaults in developer and CI environments with secrets similar to the deployed environments.
This will likely be a small standalone application and/or repository (vs being called within another app). Vault is already installed, configured, and running on the host via configuration management tool.
The examples already in the project do this vault seeding sequence very well for CakePHP apps, but I think there is an opportunity to implement some of this logic on a
Jippi\Vault\Helper
namespace very similar to the Consul SDK and be usable within any app or framework.A "Seed" helper with some convenience methods fits my current use case well:
But there may be a better name or context than "seed" from which to offer these methods.