-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can there be an external property file for Appspace ? #522
Comments
Hi @aalapargekartibco Please use |
@vpawar-ai perfect. Thanks. |
@vpawar-ai perfect. Thanks. |
@vpawar-ai Can we mention a url in the -DdeploymentConfigfile ? If I mention t like this then it is not taking it and proceeds with the configurations in the pom file. clean install -DdeploymentConfigfile=https://gitlab.com/aalapargekar/artifacts/raw/master/SimpleRest6x/prod.properties -Dhttp.agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.183 Safari/537.36" |
Externl URL for -DdeploymentConfigFile is supported in 2.8.0 |
@vpawar-ai verified, thanks |
I have generated the pom for appspace using dev box details (bwagent host, port, domain name, appnode port etc..). A lot of these details are different between dev and prod.
One option is to use java properties in maven goals, something like
clean install -Dprofile=prod.substvar -Dredeploy=true -DappSpace=xxx -DagentPort=xxx -DagentHost=xxx ........
You can see how the goal with become extremely lengthy. Is there a way to mention all these properties in an external property file instead and mention that property file in the maven goals ?
The text was updated successfully, but these errors were encountered: