Add possibility to set path to config.json file

[Kittiman]

It would be nice to be able to set the path to the config.json file this would also open up to have different config.json files / profile. config-test.json, config-prod.json etc.

It look like the path to the config.json file is hard-code.

Ex:
-Dapigee.configFile=.\foo\config.json

[ssvaidyanathan]

HI @Kittiman - you should be able to put all the environment related configurations within the same config.json. The sample config.json shows how you can have different config for each environment. The "name" property maps to the environment followed by what configuration you need under proxies, targets and policies. You can have all of those under each environment you listed within the same config.json. The plugin will pick the appropriate configurations and do the needful. Hope that clarifies

[Kittiman]

Hi, Tanks for your reply. We know that this is possible but there are case were it would be nice to be able to use one config file per environment. In some case it is easier to add a new config file for each proxy if you would need to add configuration for a new environment and you have 50 proxies. It is easier to script this. But this was not our main problem / wish. But our current problem is that we would need to be able to specify the location of the config.json file to fit our ci process and today this is not supporter.

…

----- Svarsmeddelande ----- Från: "Sai Saran Vaidyanathan" <[email protected]> Till: "apigee/apigee-deploy-maven-plugin" <[email protected]> Kopia: "Kittiman" <[email protected]>, "Mention" <[email protected]> Rubrik: [apigee/apigee-deploy-maven-plugin] Add possibility to set path to config.json file (#93) Datum: ons, maj 2, 2018 20:51 HI @Kittiman<https://github.com/Kittiman> - you should be able to put all the environment related configurations within the same config.json. The sample config.json<https://github.com/apigee/apigee-deploy-maven-plugin/blob/master/samples/forecastweatherapi-recommended/src/gateway/forecastweatherapi/config.json> shows how you can have different config for each environment. The "name" property maps to the environment followed by what configuration you need under proxies, targets and policies. You can have all of those under each environment you listed within the same config.json. The plugin will pick the appropriate configurations and do the needful. Hope that clarifies — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#93 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ASshYCu-FrtPHEQskap61kMs5kcLYzYYks5tugAwgaJpZM4TvlFO>.

[ssvaidyanathan]

Thanks for getting back. Still unclear on your explanation. Can you give me an example ? The whole point of having this within the main project is so that only the proxy's configurations are kept within this file. Not sure I get your problem. If you can provide an example, that will help. Your ask is not a big enhancement, just wondering if its needed.

[Kittiman]

Hi @ssvaidyanathan
When we use our deployment process we want to be able to deploy with maven to our sandbox environment with different username/prefix in the proxy url. This is to be able to have same proxy in sandbox for individual deployment until we merge it to our master branch.
Ex /products should be /products${suffix]
In the config.json file it is not possible to use ${} and get maven to replace this when applying this to the deployment package. We neither want to change to original config.json file that is checked in to the git repository. We want to copy the original file make the change and use this file when package, for example place this file in the target folder when running maven package.
Currently we have added a maven replace that make this change in the target folder and have excluded the proxy url part in the config.json file for our sandbox environment.
But this is the reason we thought that it would be nice to be able to tell where the config.json file is located. And this also would open up more possibility of how to handle the config.json file for different CI thinking.
We think that this would be a nice enhancement and quite an easy change, as you also did write.

[ssvaidyanathan]

We have seen customers do the replace approach. However will get back to you once we have this pushed.