[
https://issues.apache.org/jira/browse/GEODE-3635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267731#comment-16267731
]
Patrick Rhomberg commented on GEODE-3635:
-----------------------------------------
Additionally, it appears that this may be relying on underlying string
interpolation, perhaps as part of Spring, to do the actual substitution.
Testing from the command line
{noformat}
$> gfsh -e 'echo "${APP_COLLECTION_LIMIT} should be 20"'
(1) Executing - echo "${APP_COLLECTION_LIMIT} should be 20"
20 should be 20
{noformat}
Consequently, output testing via {{GfshCommandRule}} will not demonstrate the
problem.
> Echo command does not behave as documented
> ------------------------------------------
>
> Key: GEODE-3635
> URL: https://issues.apache.org/jira/browse/GEODE-3635
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
> Reporter: Patrick Rhomberg
>
> The Set Variable command does appear to set gfsh environment properties, but
> these values are only accessible by Java methods that use them. They do not
> parse in the bash style. For instance:
> {noformat}
> gfsh> set variable --name=FOO --value=bar
> Value for variable FOO is now: bar.
> gfsh> echo --string=${FOO}
> ${FOO}
> {noformat}
> Examining the implementation, there is an explicit special case of
> {noformat}
> gfsh> echo --string=$*
> {noformat}
> which will describe the current gfsh environment. Rather than this special
> case, this may be better suited to a Describe Environment command.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
