System Setting Expansion Namespaces
The default namespace when using the
${foo} system setting expansion syntax is box environment variable, Java system properties, and OS environment variables.It is also possible to leverage built-in namespaces to allow expansions that reference:
- server.json properties
- box.json properties
- arbitrary JSON file properties
- Config settings (like the
config showcommand) - Server info properties (like the
server info property=namecommand) - Other properties in the same JSON file
If the current working directory of the shell contains a
server.json file, you can reference any property in it with the serverjson. namespace.:${serverjson.name}
${serverjson.app.cfengine}
${serverjson.web.http.port}
${serverjson.trayEnable:defaultValue}
if you have a server json file with a non-default name such as
server-custom.json then you can access it with the serverjson. namespace.:${serverjson.[email protected]-custom.json}
${serverjson.app.[email protected]-custom.json}
${serverjson.web.http.[email protected]-custom.json}
${serverjson.[email protected]-custom.json:defaultValue}
If the current working directory of the shell contains a
box.json file, you can reference any property in it with the boxjson. namespace.:${boxjson.name}
${boxjson.slug}
${boxjson.testbox.runner}
${boxjson.description:defaultValue}
You can can reference properties from any JSON file with either a relative path (to the current working directory) or an absolute path with the
json. namespace..${json.myProperty.[email protected].json}
${json.myProperty.[email protected]/path/to/myFile.json:defaultValue}
You can expand any valid config setting with the
configsetting. namespace. So getting the same value you get when you run the commandconfig show endpoints.forgebox.apitoken
can be expanded like this:
${configsetting.endpoints.forgebox.apitoken}
${configsetting.endpoints.forgebox.apitoken:defaultValue}
You can expand any valid server info property with the
serverinfo. namespace. So getting the same value you get when you run the commandserver info property=serverHomeDirectory
can be expanded like this:
${serverinfo.serverHomeDirectory}
${serverinfo.serverHomeDirectory:defaultValue}
To see all the possible properties you can acess in the
serverinfo namespace, run this command:server info --json
Every key in the outputted struct is a valid
serverinfo property.By default, the expansion looks at the default server in the current working directory. To grab a server property by server name, use this syntax:
${serverinfo.[email protected]}
${serverinfo.[email protected]:defaultValue}
If a
${serverinfo.xyz} expansion is resolved in the context of a server specific package script or server script, it will use that server's details, regardless of what the current working directory is.You can self-reference other properties in the same JSON file using the
@ namespace. So given the following JSON file:{
"appFileGlobs" : "models/**/*.cfc,tests/specs/**/*.cfc",
"scripts":{
"format":"cfformat run ${@appFileGlobs} --overwrite",
"format:check":"cfformat check ${@appFileGlobs} --verbose"
}
}
The expansion of
${@appFileGlobs} self-references the appFileGlobs property inside the same file, allowing for easy re-use of that value.Modules can register an onSystemSettingExpansion interceptor to contribute custom system setting namespace expansions. The interceptor gets the following data in interceptData
- setting - The name of the setting to be expanded (with ${} and :defaultValue removed)
- defaultValue - The default value, or empty string if none specified
- resolved - A boolean that should be set true if the interceptor was able to resolve the setting
- context - A struct of the original JSON being expanded or the parameters from the command line where the expansion was used.
A hypothetical example would be:
function onSystemSettingExpansion( struct interceptData ) {
// ${luceeInfo.property}
if( interceptData.setting.lcase().startsWith( 'luceeinfo.' ) ) {
var settingName = interceptData.setting.replaceNoCase( 'luceeInfo.', '', 'one' );
interceptData.setting = server.lucee[ settingName ] ?: interceptData.defaultValue;
// Stop processing expansions on this setting
interceptData.resolved=true;
return true;
}
}
And then we would use our hypothetical namespace to reference any Lucee information like so
echo ${luceeinfo.version}
It's important if you implement your own
onSystemSettingExpansion interceptor that you check the incoming setting to see if it applies to you. If you process the system setting, you must place the final expanded value back in the interceptData.setting struct key, set interceptData.resolved to true and return true from the interception method so the chain stops processing.Last modified 24d ago