You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Steve Varnau (JIRA)" <ji...@apache.org> on 2017/11/30 21:50:02 UTC

[jira] [Assigned] (TRAFODION-2826) Reduce confusion of trafci / trafci.sh, retain compatibility

     [ https://issues.apache.org/jira/browse/TRAFODION-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Varnau reassigned TRAFODION-2826:
---------------------------------------

    Assignee: Steve Varnau

> Reduce confusion of trafci / trafci.sh, retain compatibility
> ------------------------------------------------------------
>
>                 Key: TRAFODION-2826
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2826
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: client-ci
>            Reporter: Steve Varnau
>            Assignee: Steve Varnau
>            Priority: Minor
>
> trafci was created as a developer convenience wrapper of trafci.sh, but was included in the installed product, so users now expect it to be there. We need to maintain it's usage.
> The wrapper tries to infer the server to use and defaults user/pw for the case when no LDAP security is setup.  All those defaults could be pushed into trafci.sh, and make trafci very thin wrapper.
> If client configuration file is found, either trafci or trafci.sh should pick up host from there.
> The only behavior difference should be that if there is no configuration file found, then trafci defaults to localhost as host (development environment), whereas trafci.sh will not pass any host, and the user will be prompted for hostname.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)