You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Pochatkin (Jira)" <ji...@apache.org> on 2022/06/15 11:25:00 UTC

[jira] [Assigned] (IGNITE-17130) Profilies support for CLI configuration

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

Mikhail Pochatkin reassigned IGNITE-17130:
------------------------------------------

    Assignee: Mikhail Pochatkin

> Profilies support for CLI configuration
> ---------------------------------------
>
>                 Key: IGNITE-17130
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17130
>             Project: Ignite
>          Issue Type: New Feature
>            Reporter: Mikhail Pochatkin
>            Assignee: Mikhail Pochatkin
>            Priority: Major
>              Labels: ignite-3, ignite-3-cli-tool
>
> h3. Config file site:
> The Ignite CLI currently only has one set of properties. Need to support multiple profiles, this means that the config must have multiple sections for each user profile. INI format completely covers everything we need, so need migrate config file format from properties to ini.
> Default profile name [default].
> h3. CLI command site:
> Create profile command
> {code:java}
> ignite cli config create-profile
> --name profile_name (REQUIRED) 
> --copy-from profile-name (OPTIONAL) 
> --activate true\false (OPTIONAL,  DEFAULT VALUE = true){code}
> Activate profile command as default profile
> {code:java}
> ignite cli config --profile profile_name {code}
> Read\write property with profile 
> {code:java}
> ignite cli config --profile profile_name get\set propertyKey=propertyValue {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)