Closed mwanzias closed 8 months ago
@mwanzias reach out to me or Ray Luo and we can discuss this
We discussed offline. We agreed that the samples will not provide a configuration file existing in Version Control System; instead, the automation scripts shall populate a configure file (currently a .env
) on-the-fly.
We have some automated scenarios, there are files we depend on to have the code automatically replace the tokens and configure the authority. The files seem to have been dropped in this specific edition of samples.
That is the apps.json file in the AppCreationScripts is it possible to be reinstated? there are a few structural differences between sample.json and apps.json the apps.json would be what we use for the automated replacement process for the appId, client secret and any other client specific configuraitons.
The section of interest in the apps.json file had this kind of configurations
"codeConfigurations": [ { "settingFile": ".env", "replaceTokens": { "appId": "Enter_the_Application_Id_Here", "tenantName": "Enter_the_Tenant_Subdomain_Here" } }, ]