[ 
https://issues.apache.org/jira/browse/BROOKLYN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237724#comment-14237724
 ] 

Alex Heneveld edited comment on BROOKLYN-95 at 12/8/14 10:33 AM:
-----------------------------------------------------------------

With https://github.com/apache/incubator-brooklyn/pull/373 you can now reset 
config with e.g. the following:

{noformat}
export 
NGINX_URL=http://localhost:8081/v1/applications/Y0T20UbB/entities/BXgSkgMR

curl -v -H "Content-Type: application/json" \
  -d '{ "proxy.ssl.config": { "certificateDestination": "/tmp/server.crt",  
"keyDestination": "/tmp/server.key" }, "proxy.https.port": "8453+" }'  \
  ${NGINX_URL}/config

curl -v -H "Content-Type: application/json" \
  -d '{ "proxy.https.port": "8453" }'  \
  ${NGINX_URL}/sensors

curl -v -H "Content-Type: application/json" \
  -d '{}'  \
  ${NGINX_URL}/effectors/restart
{noformat}

If you're content to use the default https port you can skip the sensor curl, 
and skip the sensor config (just setting {{proxy.ssl.config}}).  It should then 
switch to https.


was (Author: alex.heneveld):
With https://github.com/apache/incubator-brooklyn/pull/373 you can now reset 
config with the following:

{noformat}
curl -v -H "Content-Type: application/json" \
  -d '{ "proxy.ssl.config": { "certificateDestination": "/tmp/server.crt",  
"keyDestination": "/tmp/server.key" }, "proxy.https.port": "8453+" }'  \
  http://localhost:8081/v1/applications/joiteg98/entities/tyFyCgzM/config
{noformat}

And then a restart, and it will switch to https.  (If it has already detected 
port 8443, you'll have to clear the sensor for the port also.)

> support switching nginx from SSL to non-SSL
> -------------------------------------------
>
>                 Key: BROOKLYN-95
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-95
>             Project: Brooklyn
>          Issue Type: New Feature
>            Reporter: Alex Heneveld
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to