[jboss-as7-dev] Configuration conundrum with Express

[Jason T. Greene]

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 ?
>
> 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.
>
>> 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?

-- 
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat