[
https://issues.apache.org/jira/browse/IGNITE-17130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-17130:
---------------------------------------
Description:
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 profile create
--name profile_name (REQUIRED)
--copy-from profile-name (OPTIONAL)
--activate true\false (OPTIONAL, DEFAULT VALUE = false){code}
Activate profile command as default profile
{code:java}
ignite cli config profile --select-current profile_name {code}
Read\write property with profile
{code:java}
ignite cli config --profile profile_name get\set propertyKey=propertyValue
{code}
Read current profile
{code:java}
ignite cli config profile show{code}
was:
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 profile create
--name profile_name (REQUIRED)
--copy-from profile-name (OPTIONAL)
--activate true\false (OPTIONAL, DEFAULT VALUE = false){code}
Activate profile command as default profile
{code:java}
ignite cli config profile use profile_name {code}
Read\write property with profile
{code:java}
ignite cli config --profile profile_name get\set propertyKey=propertyValue
{code}
Read current profile
{code:java}
ignite cli config profile show{code}
> 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
> Fix For: 3.0.0-alpha6
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> 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 profile create
> --name profile_name (REQUIRED)
> --copy-from profile-name (OPTIONAL)
> --activate true\false (OPTIONAL, DEFAULT VALUE = false){code}
> Activate profile command as default profile
> {code:java}
> ignite cli config profile --select-current profile_name {code}
> Read\write property with profile
> {code:java}
> ignite cli config --profile profile_name get\set propertyKey=propertyValue
> {code}
> Read current profile
> {code:java}
> ignite cli config profile show{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
