enable transit secret engine at another path #67
Merged
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.
Signed-off-by: Batuhan Apaydın batuhan.apaydin@trendyol.com
I have a problem with storing keys in the Vault transit engine. cosign waits for me to enable
![Screen Shot 2021-05-26 at 20 32 19](https://user-images.githubusercontent.com/16693043/119718944-dd19c400-be70-11eb-87da-875481e15599.png)
Vault Transit Secret Engine
at pathtransit/
, but in Vault, I don’t have to enable secret engines at its default paths, so, I can override this behavior by using -path option while enabling it. So, in the scenario I have been enabled Transit Secret Engine at a different path, cosign throws an error like the following:if you want to reproduce that error above, you can type the following commands:
This PR is aiming to solve this problem that I mentioned above.