[jboss-as7-dev] Configuration conundrum with Express

[Scott Stark]

On 10/18/11 7:07 AM, Jason T. Greene wrote:
> On 10/18/11 2:43 AM, Max Rydahl Andersen wrote:
>>> So the plan, and what I'll be working on this week is to have a batch
>>> CLI script that exists in the openshift express application repository,
>>> when pushed to the express server, is run against the jbossas server 
>>> CLI
>>> interface.
>>
>> I assume this starts on a pristine new setup every time to avoid 
>> duplicate/overlapping changes ?
>>
Correct.

>> That's not the case when running against a local server thus always 
>> doing it as part as tool  deploy
>> is then not feasible IMO - having a way to easily run the script 
>> would be relevant though.
Right, so, can we have a tools "configured server" notion that takes the 
standalone.xml at a given point, a cli batch file, and overwrites the 
standalone.xml and reapplies the batch file as a configure operation? In 
general this will be different from the remote/cloud environment even if 
one can use env/system property references because I'll have my desktop 
using a different database than in the remote env for example. Maybe the 
way to handle this is to have multiple scripts, one for the commands 
common to each environment, another for the configurations that differ 
more fundamentally based on the services available in the environment.

>>
>>> One issue that is coming up is the need to refer to environment
>>> variables for things like the interfaces/ports for socket services.
>>> These values are a property of the execution environment the server is
>>> being administered in, and activation of a mysql datasource for example
>>> depends on the user "embedding" the mysql cartridge into the jbossas7
>>> openshift application. To run the same configuration against a local
>>> server in jboss tools, we would need to allow for the typical
>>> ${env-var:default} type of syntax. Right now the CLI does not do any
>>> system property or environment variable replacement. I think this is a
>>> feature that needs to be added to allow the scripts to be portable
>>> across provisioning environments.
>>
>> Agreed - this is why I was hoping AS7 would support the .cli archive 
>> notion.
>
> I think Brian's question was "Why can't we just put the env 
> expressions in the management operation?" Perhaps the CLI doesn't 
> fully use the expression type when seen?
>
I am talking about having the env expressions in the batch script of the 
management operations. The issue was that these are not being replaced 
by the command line tools.