Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to use mc without hardcoding access and secret key into config file #5056

Closed
scherepanov opened this issue Oct 2, 2024 · 2 comments
Closed

Comments

@scherepanov
Copy link

Expected behavior

I have access and secret key, and I do not want/cannot put them into file on disk.
I need to specify access and secret key as parameters to mc. Specified access and secret key will override what is hardcoded in alias.
Primary goal is to avoid having sensitive information in file on disk (.mc/config.json).
Secondary goal is to use very many pairs access key - secret key, without creating million of aliases.

Actual behavior

mc require alias that is stored in file on disk and has hardcoded access and secret key

Steps to reproduce the behavior

Check content of file .mc/config.json

mc --version

  • (paste output of mc --version)
    Most recent version

System information

Linux

@klauspost
Copy link
Contributor

@scherepanov
Copy link
Author

@klauspost thanks for taking time and answering my question.
Yes that will work perfectly well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants