Hi again @bradford.rust,
We use the same approach as well.
It has worked well for us for the past 6 months and has survived the test of time.
In our case, since we have a on premises Orchestrator we don’t worry about the number of calls to get the asset /s does (not hurt performance) but this method essentially would do the same function requested above. It’s lightweight and fast.
Just an addition: We also extend this method to config file contents which helps us update the config file in a json string format in Orchestrator. This has ensured that we do not need to edit the excel file in the release nuget package.
We use a text asset and in the performer deserialize the content to get the Jobject key-value pairs and based on Dev or Prod env choose the correct values.