i am trying to set UI properties for edge-ui as found by
grep -ri "proxy" /opt/apigee/edge-ui/source/
# WS configuration # ~~~~~ # If you need to set proxy params for WS requests # http.proxyHost = localhost # http.proxyPort = 3128 # http.proxyUser = jojo # http.proxyPassword = jojo
When i set these in /opt/apigee/customer/application/edge-ui.conf they do not seem to get picked up. Is that by design?
Solved! Go to Solution.
You can follow the below steps to achieve this:
1. Create /opt/apigee/customer/application/ui.properties
2. Put these values in /opt/apigee/customer/application/ui.properties
conf/application.conf+http.proxyHost=localhost conf/application.conf+http.proxyPort=3128 conf/application.conf+http.proxyUser=jojo conf/application.conf+http.proxyPassword=jojo
3. Restart the edge-ui (apigee-service edge-ui restart)
Thanks,
Archendra
You can follow the below steps to achieve this:
1. Create /opt/apigee/customer/application/ui.properties
2. Put these values in /opt/apigee/customer/application/ui.properties
conf/application.conf+http.proxyHost=localhost conf/application.conf+http.proxyPort=3128 conf/application.conf+http.proxyUser=jojo conf/application.conf+http.proxyPassword=jojo
3. Restart the edge-ui (apigee-service edge-ui restart)
Thanks,
Archendra
So - this is great and all - but how the heck are we supposed to know this based on what was in the guides?
I apologies for not getting it documented properly. We'll update the documents to reflect the same. @sgilson please update the docs.
@archendra i for one am rather put off by this new system of managing configuration entries - especially considering the effort we had to put in to manage these manually w/ puppet.
being told "you are on your own on this one" and then suddenly having it all renovated behind the scenes to use a non standard and quite difficult to follow set of custom constraints just feels like a bad idea.
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |