Is there any way to modify the dab config file on publish?

[Julian Dormon (julianadormon)]

Is there any way to modify the dab config file on publish?

[Davide Mauri (yorek)]

What do you mean by "publish"?

[Julian Dormon (julianadormon)]

My Dab config file is part of my website's project files. When I publish a staging version, I have a different connection string than in production. I was thinking something kind of like using transforms in web.config? Thanks.

[Davide Mauri (yorek)]

In addition to what Aniruddh Munde (@Aniruddh25) said, you also have other two options. If you are deploying using Static Web Apps, you're already good to go as you can have different environments, each with its own connection string. (And every PR as a dedicated environment too!): https://learn.microsoft.com/en-us/azure/static-web-apps/preview-environments

If you are not using Static Web Apps, you can use different configuration files by setting the environment variable DAB_CONFIG so that for each environment it will tell DAB to load the correct configuration file. For example: dab-config.Development.json: https://learn.microsoft.com/en-us/azure/data-api-builder/configuration-file#environments-support

[Aniruddh Munde (Aniruddh25)]

Hi Julian Dormon (@julianadormon),

Perhpas, you could use the feature to replace environment variables with their values based on your staging/production version:

1. use @env('connection-string') in the config.
2. Set the value of connection-string to be different for different environments.
3. One way you could set this is to add different .env files in the same directory as the config file for different environments holding different values to the environment variable connection-string

For more details, see here: https://learn.microsoft.com/en-us/azure/data-api-builder/configuration-file#setting-environment-variables

[Julian Dormon (julianadormon)]

Thank you for this!