0
|
1 |
ConE export action
|
|
2 |
==================
|
|
3 |
Running action export
|
|
4 |
Usage: cone export [options]
|
|
5 |
|
3
|
6 |
The export functionality exports configurations from the current project to a remote project. Default value for the current project is the currently working directory. A project can be either a folder or a CPF/ZIP file or even a Carbon webstorage (via ExtAPI).
|
0
|
7 |
|
|
8 |
Examples
|
|
9 |
--------
|
|
10 |
|
3
|
11 |
**Export a configuration from configuration project folder to a zip file**::
|
0
|
12 |
|
|
13 |
>cd configproject_root
|
|
14 |
>cone export -c configuration_root.confml --remote=exported.zip
|
|
15 |
|
|
16 |
or use the option -p|--project to point to the configuration project root::
|
|
17 |
|
|
18 |
>cone export --project=configproject_root --remote=exported.zip -c configuration_root.confml
|
|
19 |
|
|
20 |
**Export a configuration from a zip|cpf file to a folder**
|
|
21 |
|
|
22 |
The different to the previous example is that the project parameters are turned otherway around. ::
|
|
23 |
|
|
24 |
>cd configproject_root
|
|
25 |
>cone export --project exported.zip --remote=. -c configuration_root.confml
|
|
26 |
|
|
27 |
**Export a configuration from a webstorage (carbon) file to a folder**
|
|
28 |
|
|
29 |
The Carbon functionality will be released in ConE 1.2 release and is not yet officially available.
|
|
30 |
The usage is similar to the previous, but the carbon path is given as http://serverpath/extapi.::
|
|
31 |
|
|
32 |
>cd configproject_root
|
|
33 |
>cone export --project http://carbonqa.nokia.com/extapi -r . -c configuration_root.confml
|
|
34 |
|
|
35 |
See the info action for getting a list of available configurations inside Carbon.
|
|
36 |
|
|
37 |
**Export a configuration from a folder to webstorage (carbon)**::
|
|
38 |
|
|
39 |
>cd configproject_root
|
|
40 |
>cone export --remote http://carbonqa.nokia.com/extapi -c configuration_root.confml
|
|
41 |
|
3
|
42 |
**Export a configuration and run a action during the export**::
|
|
43 |
ConE can also run separate actions during the exporting for example to fix model level errors if possible. To run for example the fix step during export you can use --run-action=fix attribute.
|
|
44 |
|
|
45 |
>cd configproject_root
|
|
46 |
>cone export -c configuration_root.confml --remote=../export_folder --run-action=fix
|
0
|
47 |
|
|
48 |
|
|
49 |
Options list
|
|
50 |
------------
|
3
|
51 |
Options:
|
0
|
52 |
--version show program's version number and exit
|
|
53 |
-h, --help show this help message and exit
|
|
54 |
--print-settings Print all the default settings from the current
|
|
55 |
setting container.
|
|
56 |
--print-supported-impls
|
|
57 |
Print all supported ImplML XML namespaces and file
|
3
|
58 |
extensions.
|
|
59 |
--print-runtime-info Print runtime information about ConE.
|
0
|
60 |
-v LEVEL, --verbose=LEVEL
|
|
61 |
Print error, warning and information on system out.
|
|
62 |
Possible choices: Default is 3.
|
|
63 |
NONE (all) 0
|
|
64 |
CRITICAL 1
|
|
65 |
ERROR 2
|
|
66 |
WARNING 3
|
|
67 |
INFO 4
|
|
68 |
DEBUG 5
|
|
69 |
--log-file=FILE Location of the used log file. Default is 'cone.log'
|
3
|
70 |
--log-config=FILE Location of the used logging configuration file.
|
|
71 |
Default is 'logging.ini'
|
|
72 |
--username=USERNAME Username for webstorage operations. Not needed for
|
|
73 |
filestorage or cpf storage. If the username
|
|
74 |
is not given, the tool will use the logged in
|
|
75 |
username. Example: cone export -p webstorage_url -r .
|
|
76 |
-c sample.confml --username=admin --password=abc123.
|
|
77 |
--password=PASSWORD Password for webstorage operations. Not needed for
|
|
78 |
filestorage or cpf storage. If the password
|
|
79 |
is not given, the tool will prompt for password if
|
|
80 |
needed.
|
0
|
81 |
-c CONFIG, --configuration=CONFIG
|
3
|
82 |
Defines the name of the configuration for the action,
|
|
83 |
can be specified multiple times to include multiple
|
|
84 |
configurations.
|
|
85 |
--config-wildcard=WILDCARD
|
|
86 |
Wildcard pattern for including configurations, e.g.
|
|
87 |
product_langpack_*_root.confml
|
|
88 |
--config-regex=REGEX Regular expression for including configurations, e.g.
|
|
89 |
product_langpack_\d{2}_root.confml
|
0
|
90 |
-p STORAGE, --project=STORAGE
|
|
91 |
defines the location of current project. Default is
|
|
92 |
the current working directory.
|
|
93 |
|
|
94 |
Export options:
|
3
|
95 |
The export action is intended for exporting configurations from one
|
|
96 |
project (storage) to another. A project can be a folder, a CPF or ZIP
|
|
97 |
file, or a Carbon web storage URL.
|
|
98 |
Two different ways of exporting are supported:
|
|
99 |
1. Exporting multiple configurations into one new project using
|
|
100 |
--remote
|
|
101 |
2. Exporting configurations into a number of new projects using
|
|
102 |
--export-dir
|
0
|
103 |
|
|
104 |
-r STORAGE, --remote=STORAGE
|
3
|
105 |
Defines the location of remote storage. All
|
|
106 |
configurations included using --configuration,
|
|
107 |
--config-wildcard and --config-regex are exported into
|
|
108 |
the storage. If the remote storage location is not
|
|
109 |
given, the default location is determined based on the
|
|
110 |
first included source configuration name. E.g.
|
|
111 |
'example.confml' would be exported into 'example.cpf'
|
|
112 |
--export-dir=EXPORT_DIR
|
|
113 |
Defines the directory where each included
|
|
114 |
configuration is exported as a new project.
|
|
115 |
--export-format=EXPORT_FORMAT
|
|
116 |
Defines the format into which projects are exported
|
|
117 |
when using --export-dir. Possible values are 'cpf'
|
|
118 |
(the default) and 'dir'.
|
|
119 |
-a CONFIG, --add=CONFIG
|
|
120 |
Adds a configuration layer to the given configuration
|
|
121 |
as last element. The add operation can be used several
|
0
|
122 |
times in a single command and it can create even an
|
3
|
123 |
empty layer. Example --add foo/root.confml --add bar
|
0
|
124 |
/root-confml.
|
3
|
125 |
--run-action=PLUGIN
|
|
126 |
Adds a execution of extra step that can manipulate the
|
|
127 |
configuration before it is exported to external
|
|
128 |
storage. The --run-action operation can be used
|
|
129 |
several times in a single command and it will execute
|
|
130 |
the actions in given order.Example --run-action=fix,
|
|
131 |
which would execute fix action during export.
|
|
132 |
--exclude-folders Excludes empty folders from export
|