You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Essentially what we want here is that I as a developer, should be able to run the tests on these samples without modifying them to confirm they still work. However unless I'm on the team maintaining the samples, I likely don't have access to the resources it's tested with. By using env variables means all I need to do when running locally is change the env var, and not worry about changing the model ids when there is a problem.
So something like this is perfectly acceptable:
resource_id=os.getenv("YOUR-RESOURCE-NAME")
For bonus points you can include a link to instructions for creating the resource, if you really want to make it accessible for other developers.
Essentially what we want here is that I as a developer, should be able to run the tests on these samples without modifying them to confirm they still work. However unless I'm on the team maintaining the samples, I likely don't have access to the resources it's tested with. By using env variables means all I need to do when running locally is change the env var, and not worry about changing the model ids when there is a problem.
So something like this is perfectly acceptable:
For bonus points you can include a link to instructions for creating the resource, if you really want to make it accessible for other developers.
Originally posted by @kurtisvg in #13 (comment)