Could this not be done with the config pathway of setting headers in an OTE Service client as of now? Or are you thinking of something more specialized/pre-configured options?

For the config pathway, I mean something like:

from otelib import OTEClient

auth_client = OTEClient("https://api.ote-service.app", headers={"Authorization": "Bearer <token>"})

Where the actual token can then be loaded from a .env file or from a set environment variable or whatever?

Hmm, but if the key is to do login, etc, then the whole workflows should be different.

Yes, sourcing the token from an .env file might be a much smarter and secure way than hardcoding it into a the script where you execute the pipeline.

However, this also might be limited if you would like to manage different access control parameters over different strategies. E.g. DataResourceConfig A takes token No 1 and TransformationConfig B takes token No 2.

If you do not specify it in the config while creating the strategies, the ote-services will by default take the token from the headers of the incoming request. This might become problematic in that way, that the wrong token might be passed to the wrong strategy when executing the pipeline.

Hence, if we would like to manage this more dynamically in a pydantic-setting, I think it makes sense to have to opportunity to manage all secrets this settings-object and map them there to all the strategies we would like to pass them later on.

But this is definitely a larger effort to implement this and I don't know in how far the otelib is intended to solve this procedure.