Furthermore, instead of hardcoding the default port value in the deploy.sh
script, we can find that out from the
[product-name]-default-service.yaml file, using the following bash command.
This way, if the user changes the NodePorts for the product, they are not
required to repeat it in the script. It's easy to miss this change and get
frustrated when the deploy script doesn't work.
Con: there shouldn't be any major YAML changes, otherwise the grep -A
command might fail.
cat ${PWD##*/}-default-service.yaml | grep servlet-https -A 4 | grep
nodePort | awk '{print $2}'
Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Fri, Apr 22, 2016 at 10:31 AM, Thanuja Uruththirakodeeswaran <
[email protected]> wrote:
>
>
> On Fri, Apr 22, 2016 at 10:09 AM, Chamila De Alwis <[email protected]>
> wrote:
>
>> Hi,
>>
>> Just noticed that, in the README [1], we instruct the user to add a host
>> mapping manually to access the management console after deploying the
>> Service. We can do this in the deploy script itself, and cleanup in the
>> undeploy script. WDYT?
>>
>
> +1, It'll easy the process.
>
>>
>> [1] -
>> https://github.com/wso2/kubernetes-artifacts/blob/master/wso2am/README.md
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Software Engineer | WSO2 | +94772207163
>> Blog: code.chamiladealwis.com
>>
>>
>>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
