Repository navigation
CLI tool for more use-cases #13
Description
I would like to create the CLI, I have a previous expreiance to build it, also consider the options
That I told you about that, api can response text
As we could make it export the env and inject them to the system or we can leave this to the CLI,
This is would make a point for us cause there's no tool for that
Originally posted by @Mahmoudgalalz in #3 (comment)
Activity
chronark commentedon Jan 17, 2023
Yes, I think building a cli is the next step after the API
chronark commentedon Jan 17, 2023
I've had a great experience using
oclifto build a CLI in the pastProbably I would split this up into different packages and manage it using turborepo
Or similar
I can take a better look tonight
Mahmoudgalalz commentedon Jan 17, 2023
I would like to start with you, we should cosider the size of it and its performance, some CI/CD tools as pricing as pay as you go, so we should cosider that, let me know to collaborate in this together 🦀
chukwumaokere commentedon Jan 17, 2023
So just brainstorming the CLI functionality here.
One would probably use it something like this:
envshare share some-pre-encrypted-secret --reads=999 --ttl=7 --units=daysand get a response like...
URL: https://envshare.dev/unseal#{id} Id: {id} Expires In: 7 days Expires At: January 24, 2023 19:41:33 (UTC) Reads: 999and maybe can do
envshare unseal --id={id}And receive a response like
Does that look sound right for the functionality or were you guys planning something else? 🤔
Mahmoudgalalz commentedon Jan 18, 2023
for the cli tool, actually we need to export them directly to the system, and the developer should be able to share env file
and the purpose of the cli tool, just to config a server, the seal and unseal will happen between a Developer and an Instance (server)
envshare share --file ./src/.env --reads=10 --ttl=7 -dthe unseal, would be like
envshare inject {id}if the variables, doesn't have export we should put it after each newLine, and then output
envshare get {id}this one will output the regular output and he can do any thing later like grep then assign it to a variable etc.
chronark commentedon Jan 18, 2023
There should be 2 groups right now I think
env share ...: upload pre-encrypted data with ttl and readsenv encrypt: generate key on the client, encrypt and upload the encrypted data + iv, then display the id and full link@Mahmoudgalalz
Sounds good, what did you have in mind?
Also let's consider the use of piping entire .env files
Also a
--jsonflag would be very good to return the data in machine readable format for CIMahmoudgalalz commentedon Jan 18, 2023
we will consider using go, as its good to distribute, also I will start building it, we will rely on the api, so the API should have the options
and anything else will be within the CLI
chronark commentedon Jan 18, 2023
haha I was about to mention go with cobra for example
I love using that
api is ready btw, check the readme for the api contract
Mahmoudgalalz commentedon Jan 18, 2023
I will, and I will mention you when I setup everything and make the first req from the CLI