|
7 | 7 | downloads
|
8 | 8 | automation
|
9 | 9 | debugging
|
| 10 | +sync |
| 11 | +encryption |
10 | 12 | """
|
11 | 13 |
|
12 | 14 | config = """
|
|
104 | 106 | automation = f"""
|
105 | 107 | To import data to your TSD project(s) in an automated way,
|
106 | 108 | you firstly need to organise access for your machine(s) to the TSD API,
|
107 |
| -by proividing an IP address/range. If your machine(s) are located on |
108 |
| -an Uninett network, then TSD's current security policy allows |
109 |
| -enabling access without issue. You still need to contact USIT |
110 |
| -to get your IP whitelisted. |
| 109 | +by proividing an IP address/range. |
111 | 110 |
|
112 |
| -If not, then you will have to provide a description of how you |
113 |
| -secure your machine(s) and include it in the risk analysis of your project. |
| 111 | +Given that this level of access is taken care of, you need an API key |
| 112 | +to authenticate with. There are two ways of doing this. The first and |
| 113 | +easiest way is to is to run: |
114 | 114 |
|
115 |
| -Given that this level of access is taken care of, that you have registered tacl, |
116 |
| -and that you have obtained TSD credentials for your project(s), |
117 |
| -you can set up automated data import in the following way: |
| 115 | + tacl --register |
| 116 | +
|
| 117 | +and then to run: |
118 | 118 |
|
119 | 119 | tacl p11 --basic --upload myfile
|
120 | 120 |
|
121 |
| -The above example supposes that you have registered your client as |
122 |
| -described in the tacl --guide config section. This is suitable when |
123 |
| -you have a small number of clients. If, however, you have so many clients |
124 |
| -that registering them one-by-one is impractical, you can contact TSD |
125 |
| -at {HELP_URL} |
126 |
| -and request a standalone API client. This will give you an API key |
127 |
| -which you can use with tacl as such: |
| 121 | +This allows using the API key which is tied to your user to automate |
| 122 | +data imports. |
| 123 | +
|
| 124 | +Another use case is to use an impersonal API key, to automate |
| 125 | +data imports, and possibly exports. Contact USIT at {HELP_URL} |
| 126 | +and request a standalone API client. |
| 127 | +
|
| 128 | +This will give you an API key which you can use with tacl as such: |
128 | 129 |
|
129 | 130 | tacl p11 --api-key $KEY --upload myfile
|
130 | 131 |
|
| 132 | +You can also store the key in a file (only the key no newlines), |
| 133 | +and invoke tacl as such: |
| 134 | +
|
| 135 | + tacl p11 --api-key @path-to-file --upload myfile |
| 136 | +
|
131 | 137 | Invoking tacl like this will over-ride any other local config.
|
132 | 138 | """
|
133 | 139 |
|
|
0 commit comments