Skip to content

Move from env params to cli params only#123

Merged
deitch merged 2 commits intolf-edge:masterfrom
europaul:no-eng-params
Jan 23, 2024
Merged

Move from env params to cli params only#123
deitch merged 2 commits intolf-edge:masterfrom
europaul:no-eng-params

Conversation

@europaul
Copy link
Copy Markdown
Contributor

Adam used to get it's certificates and keys through envs. To unify the UX we switch this mechanism to getting paths to files with certificates and keys through the CLI parameters only.

@giggsoff
Copy link
Copy Markdown
Collaborator

Can you please elaborate why this change required by lf-edge/eden#927 (comment)? Looks like we had 3 options to pass certificates before (path to cert in cli, path to cert in ENV and certificate in ENV), but you remove the last, while still using the first.

@deitch
Copy link
Copy Markdown
Contributor

deitch commented Jan 17, 2024

I am not sure that it is required. The structure was confusing, though. You provide a file path to a cert, which by default is inside the database path, but is used even if the database is not on disk (e.g. redis or in memory), and then write to that path. I think @europaul's approach makes his straightforward, and like most certificate-based software: provide paths to certs/keys via CLI, software reads it. No confusion about what is provided in alternate approach.

It isn't just the env var. If we had --cert-path and --cert-content, it would be equally confusing.

@europaul
Copy link
Copy Markdown
Contributor Author

@giggsoff @deitch you are right, this change is not required. It is more of a clean-up like @deitch explained. Also the envs were potentially overwriting files on disk, which I think is not desirable.

lib io/ioutil

Signed-off-by: Paul Gaiduk <paulg@zededa.com>
@giggsoff
Copy link
Copy Markdown
Collaborator

Got it, thank you! Please remove the line from readme as well.

Signed-off-by: Paul Gaiduk <paulg@zededa.com>
@deitch
Copy link
Copy Markdown
Contributor

deitch commented Jan 18, 2024

Let us know when you are ready to go with this @europaul .

Any other comments @giggsoff ?

@europaul
Copy link
Copy Markdown
Contributor Author

Let us know when you are ready to go with this @europaul .

We need to merge lf-edge/eden#927 before we can merge it (unless we don't increment the Adam version, so that Eden ends up using the old version by default).

@deitch
Copy link
Copy Markdown
Contributor

deitch commented Jan 18, 2024

We need to merge lf-edge/eden#927 before we can merge it (unless we don't increment the Adam version, so that Eden ends up using the old version by default).

OK, so we can wait on that. Also want to see if @giggsoff has anything else here

@europaul europaul mentioned this pull request Jan 22, 2024
@deitch
Copy link
Copy Markdown
Contributor

deitch commented Jan 23, 2024

If @giggsoff approved and I approved and @uncleDecart did it, I see no reason to wait on the merge. :-)

@deitch deitch merged commit a7f31ed into lf-edge:master Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants