You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Zachary Blanco (JIRA)" <ji...@apache.org> on 2015/06/01 22:06:17 UTC

[jira] [Updated] (KNOX-547) Topology Validation in Knox CLI

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

Zachary Blanco updated KNOX-547:
--------------------------------
    Attachment: KNOX-547-docs.patch
                KNOX-547-3.patch

[~kevin.minder], I've taken your feedback and integrated it into the KNOX-547-3 patch. It addresses all of the issues you've mentioned. I've also gone ahead and added the commands to the docs too. See KNOX-547-docs.patch

> Topology Validation in Knox CLI
> -------------------------------
>
>                 Key: KNOX-547
>                 URL: https://issues.apache.org/jira/browse/KNOX-547
>             Project: Apache Knox
>          Issue Type: New Feature
>          Components: KnoxCLI
>            Reporter: Zachary Blanco
>            Assignee: Zachary Blanco
>            Priority: Minor
>         Attachments: KNOX-547-2.patch, KNOX-547-3.patch, KNOX-547-docs.patch, KNOX-547.patch
>
>
> Topology configuration or misconfiguration are common support cases and pain points for users of Knox.
> Create a new command in the Knox CLI utility to check the validity of a topology file.
> Not specifying /path/to/file could default to /etc/knox/conf/topologies/default.xml.
> This feature should allow a user to test the syntax of a topology file, a "shallow" validation. It does not have to check the validity of the contents.
> This feature would also become part of the Knox support checklist in support and would speed up time to resolution when.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)