We have handled this in a variety of ways and each has pros and cons:
1. Setup the values in the key vault / secret scopes. As we have an AKV aligned to each environment workspace it also allows us to pass in those environment variables. Downside is that they are all redacted so can be a pain during debugging sometimes.

2. Store them in a table - as we have a default catalog for each workspace we can vary the values in the table. Although as they are stored as Delta tables they are not necessarily the quickest.

3. Store them in a json file and read that in to python. That can be stored in a volume or path on the data lake etc.

4. When using ADF - pass in the values through widgest and make use of the ADF environment varibales function.

Hope that helps