oh, right, I get that, thanks 🙂 So my repo is usually just built with the yaml, so for now, I don’t have a requirements.txt in the repo, since it’s not needed. But for the time being, I’ll just parse the requirements from the yaml file and add them with add_requirement() , thanks for the insight 🙂

I wanted to access an Azure Storage Blob via an SAS token string, since this is how we built the codebase.

no, it’s a command-line argument now. Bc if it was in the code, it would be logged by github and I wanted to avoid having an access token logged in plaintext. That’s why argparse seemed to be nice to transfer it via commandline and not via code.
I tried parsing - storing as environment variable - deleting the parser object, but this wouldn’t work unfortunately

yes, I also saw that, but unfortunately the clearml.config of my remote machine is stored in Azure as well, so we’d have the same access/permission/authentication problem again.
But thank you for your input!

yes, that would be the solution which would make the most sense, thanks a lot! 🙂

yeah, so I want to do Task.create(reqirements_file=‘/path/to/file/requirements.yml’), but I think I’ll just parse it manually then

sure 🙂 an access token for an Azure storage blob. I could also just do more granular tokens with a smaller lifespan, but I was wondering if there is another solution

hm, I see. Thank you! Do you see an option of transferring a simple, untracked file with execute_remotely() ? If this config file wouldn’t be tracked by github (so not part of the repo) then it would solve my problem

Me again, SuccessfulKoala55 : would you also see an option for achieving this without having the token/string logged into clearml in plaintext? With argparse it’s stored as hyperparameter unfortunately.. Could I somehow prevent the logging of argparse by deleting the parser or such?

thank you so much SuccessfulKoala55 ! 🥳 Accessing the variables with sys.argv didn’t work, but using argparse is working just fine!