diff --git a/datasources/src/main/resources/template/dataSourceManagement.html b/datasources/src/main/resources/template/dataSourceManagement.html index 582107a9f..183fbfd11 100644 --- a/datasources/src/main/resources/template/dataSourceManagement.html +++ b/datasources/src/main/resources/template/dataSourceManagement.html @@ -6,8 +6,6 @@
- -<<<<<<< HEAD @@ -24,361 +22,11 @@ , hasWriteRights : hasWriteRights } var app = Elm.DataSources.init({ node: main, flags: initValues}); -======= - - -
-
-
-
-

- {{selectedDatasource.name}} - New data source - Unnamed - - -

-
-
- -
-
- -
-
- - - - - -
-
-
-
-

{{selectedDatasource.description}}

-
-
- - - -
-
-
- - - Name is required -
-
- -
Key name cannot be modified after creation.
- - -
- The key name will be used to access imported data, such as
${node.properties[{{selectedDatasource.id ? selectedDatasource.id : "key_name"}}]}
-
- Key name is required -
-
- - -
-
- -
- -
-
-
- -
- - -
-
-
- - -
-
- - -
- You can use Rudder variable expansion (
${rudder.node.xxx}, ${rudder.param.xxx}, ${node.properties[xxx]}
) here. They will be replaced by their values for each node at the time the HTTP query is run. -
-
-
- - -
-
- -
- - -
-
- When a JSON document is returned, you can define a JSON path expression (see documentation) to select only a sub-part of the document as the actual data to use as a node property. -
-
-
- - -
-
- - -
-
- - -
-
-
-
- -
-

Node properties data sources

-

- Nodes have properties that can be used to create groups or in techniques and directives parameters. - These properties are key/value pairs, where values can be a simple string or a well formed JSON document. -

-

- You can automatically import node properties by creating data sources that will query a third party REST API to retrieve data and it in a given property key for each node it's available for. -

-

-
- -
- - - - - ->>>>>>> branches/rudder/7.3