Technical lineage password manager integration design
Warning The CLI lineage harvester is now deprecated and will officially reach its end-of-life on July 31, 2026. To ensure a smooth transition, we encourage you to begin creating technical lineage via Edge, if you haven't already.
When you run the CLI lineage harvester, you can either:
-
Enter the passwords in the terminal. The passwords are then encrypted and stored in /config/pwd.conf.
- Provide the passwords via command line, in a prescribed JSON structure via stdin. This allows you to store the passwords locally in your password manager, instead of in your lineage harvester folder.
This topic provides guidance on how to structure the JSON file and which commands to use, to store the passwords locally in your password manager.
Structure of the JSON file
If you prepare a JSON file with your passwords, you have to name the file passwords.json.
The JSON file must have two sections:
-
The
catalogssection defines the connection information and credentials to your Collibra Platform instance. - The
sourcessection defines the connection information and credentials to your data sources. You use the same "id" as specified in theidproperty of the lineage harvester configuration file.
The JSON file must have the following structure:
{
"catalogs": [
{
"url" : "<url-to-collibra-cloud>",
"username":"<username-to-sign-in-to-collibra>",
"password": "<password-to-sign-in-to-collibra>"
}
],
"sources": [
{
"id": "<id-of-your-database>",
"username": "<database-username>",
"password": "<database-password>"
}
]
}
Examples of commands
When you run the CLI lineage harvester, you can use one of the following commands to provide the passwords:
|
Passwords location |
Command |
|---|---|
| A locally stored JSON file. |
Copy
|
| A custom script, for example from a password manager. |
Copy
Note Depending on your password manager, you might need different parameters. For example, see the LastPass documentation for the parameters needed by LastPass. |