You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: ProductionGuide.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# impt Production Guide #
2
2
3
-
**NOTE:** The contents of this guide have **NOT** been updated with the release of v2.5.0 (support for DUT device groups), and so some of the contents may be out of date.
3
+
**NOTE:** The contents of this guide have **NOT** been updated with the release of v2.5.0 and above (support for DUT device groups), and so some of the contents may be out of date.
4
4
5
5
This additional guide is intended for those customers who use *impt* with [production processes](https://developer.electricimp.com/manufacturing). You may use scripts on top of *impt* commands to automate some of the operations.
Copy file name to clipboardExpand all lines: README.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ Call `impt --version` or `impt -v` to display the version of the installed *impt
46
46
47
47
```bash
48
48
> impt --version
49
-
2.5.0
49
+
2.5.1
50
50
```
51
51
52
52
## Proxy Setup ##
@@ -314,7 +314,7 @@ Response body: {
314
314
}
315
315
}
316
316
Product "TestProduct" is created successfully.
317
-
Product:
317
+
Product:
318
318
id: 4e264cef-3316-cdfa-7f39-7a5d458994b3
319
319
name: TestProduct
320
320
IMPT COMMAND SUCCEEDS
@@ -365,7 +365,7 @@ The Command Execution Context rules (how *impt* determines authentication and ot
365
365
impt auth login --lk <login_key>
366
366
```
367
367
368
-
or by an account identifier:
368
+
or by an account identifier:
369
369
370
370
```bash
371
371
impt auth login --user <user_id> --pwd <password>
@@ -412,13 +412,13 @@ The `IMPT_LOGINKEY`, `IMPT_USER`, `IMPT_PASSWORD`, `IMPT_ENDPOINT` variables may
412
412
- You may have as many different [local auth files](./CommandsManual.md#local-auth-file) as you want and run *impt* commands with different authentication information in parallel (eg. for different projects/products) by running them from different processes (eg. consoles). But you should note that a [local auth file](./CommandsManual.md#local-auth-file) affects commands called from the directory where the file is located only, not from sub-directories.
413
413
414
414
- If you want to run *impt* commands in parallel in different processes (eg. consoles) with different authentication information and call them from any directory, you can utilize the [environment variables](./CommandsManual.md#auth-environment-variables):
415
-
415
+
416
416
- Option 1 — Create the required number of [auth files](./CommandsManual.md#auth-files) with different authentication information; in every process specify its own path to the required auth file using the `IMPT_AUTH_FILE_PATH` environment variable.
417
417
418
418
- Option 2 — In every process specify its own required authentication information using the `IMPT_LOGINKEY`, `IMPT_USER`, `IMPT_PASSWORD` and `IMPT_ENDPOINT` environment variables.
419
419
420
420
- If you do not want to have the user credentials visible in the console (shell) history, call the [login command](./CommandsManual.md#auth-login) without specifying the credentials; *impt* will prompt to enter them.
421
-
421
+
422
422
- If you do not want to store any authentication information in files, use the `IMPT_LOGINKEY`, `IMPT_USER`, `IMPT_PASSWORD` and `IMPT_ENDPOINT` environment variables for authentication.
423
423
424
424
- At any time and in any directory you can get the execution context currently applicable to this directory and the login status. Call the [`impt auth info`](./CommandsManual.md#auth-info) command from the required directory. The returned information includes a type of the authentication applicable to the current directory, access token status, account ID and other details.
@@ -440,7 +440,7 @@ Choose authentication method:
440
440
(2) Login Key
441
441
Enter 1 or 2: 1
442
442
Enter username or email address: username
443
-
Enter password:
443
+
Enter password:
444
444
Global login is successful.
445
445
IMPT COMMAND SUCCEEDS
446
446
```
@@ -527,7 +527,7 @@ If you want to use this feature, please read the [Commands Manual](./CommandsMan
527
527
528
528
When it is hard to uniquely specify an entity without knowing the entity ID, use [entity listing](#entity-listing-and-ownership) commands to view the entities basing on some attributes, choose the required entity and use its entity ID in the required command.
529
529
530
-
For some impCentral entities, such as Products and Device Groups, *impt* provides the ability, when using hierarchical identifiers, to identify them solely by their name. This is particularly helpful when you are developing scripts: you can pass the name of an entity and then call all manipulation commands with that entity (create, update, delete, etc.) without first obtaining the ID of the entity. The format and details of every concrete hierarchical identifier are described in the [Commands Manual](./CommandsManual.md#entity-identification).
530
+
For some impCentral entities, such as Products and Device Groups, *impt* provides the ability, when using hierarchical identifiers, to identify them solely by their name. This is particularly helpful when you are developing scripts: you can pass the name of an entity and then call all manipulation commands with that entity (create, update, delete, etc.) without first obtaining the ID of the entity. The format and details of every concrete hierarchical identifier are described in the [Commands Manual](./CommandsManual.md#entity-identification).
531
531
532
532
##### Example 1: An entity is found successfully**
0 commit comments