-
Notifications
You must be signed in to change notification settings - Fork 23
Install via package managers #27
Comments
Just released the brew tap! 🎉 You can now install secrethub using: brew install secrethub/tools/secrethub-cli |
Not really a package manager, but an @florisvdg already started work on this I see #58 |
+1 on the MSI installer. That reminds me of another update for Windows users. You can now install using Scoop:
🎉 |
We have added the CLI to snap as well 🎉 |
yum support is added in v0.29.0. |
And release v0.29.0 added |
An MSI for
|
SecretHub is now also in the Arch User Repository under the name yay -S secrethub-cli |
please add this to specific languages package-managers (e.g. npm). why? as this is used locally on the developer machines in specific projects, it will be easier to install this part of the dev-dependencies of the project. so the developer won't need to manually install it on his machine. but in most cases, a developer that has a small task on a side-project, doesn't want to deal with specific external tools that the project needs. |
Ah that's a very valid use case @stavalfi I didn't think of it that way yet, but yes it makes quite a bit of sense to have it as a project dependency,. One thing though, the dev would need a secrethub account to be able to work with it so there is that 'hidden' dependency. What's your take on that? |
thanks for the quick response :) I started to use secrethub just couple of days ago so my opinion may not be based on expirience or usage statistics, and I also don't have any expirience in managing secrets overall. so please ignore it me you think otherwise. in short, you can use the package manager to execute secrethub executable. the long version: As I understand, some (or most/all) of the team-members won't have much (or any) work to do on secrethub directly besides running a script from package.json that runs the project's tests using secrethub run command. In node and javascript, we run commands using the package manager so each script will able to run any executable it needs without worring if the executable is in the PATH or not. so, for example, if I'm using yarn, I will login by running: In addition, in ci-systems and in dockerfiles, I won't need to manage the secrethub installation seperatly. so I think I can't find a use case to not install it from the language-package-manager unless part of your job is to manage the secrerts for the project/company. |
Hi @stavalfi, very interesting use case! It would indeed be awesome if any new team member can just run an npm command to set everything up! To set everything up I think we need to do the following:
InstallationIf we add SecretHub installation via npm, we will be able to do the first step. Provision a CredentialThis relates a bit to the conversation we've had here: #297. In order to run SecretHub commands, the CLI should have access to a credential. You can see this credential as the "login" of an account. The credential is used both to authenticate to the SecretHub servers and for the encryption of your secrets. Now there's several ways to get your hands on a credential:
For your use case, I think we could use Now for the CI setup, you could provision a Now, to be able to always run this In that case your npm command could look something like this: Get Access to the SecretsNow, one last remaining challenge is that if the new teammate signs up with the I can imagine a process where the new teammate can request access, after which an admin can approve that request so that they can proceed. In that case we could add an additional SecretHub command to your npm command which checks if the current account has access to the secrets it needs and requests access if not so. Then the request for access would be included in the single npm command a new teammate would have to run to get started with SecretHub. I'll think about this a bit more and discuss in our team to see if/how this could work and how we can make the onboarding process as smooth as possible. If there's any information you can share on how you envision the onboarding process, that's really welcome! |
You can now install SecretHub via npm: https://www.npmjs.com/package/@secrethub/cli npm install @secrethub/cli |
We'd like to distribute the CLI via package managers, so that it can be easily installed using the package manager you are used to.
e.g.
We'd like to support at least:
Other package managers we are considering are:
We might add other package managers to this list. Please let us know if there's another package manager in which you'd like us to distribute the CLI.
The text was updated successfully, but these errors were encountered: