vorto | Vorto Project - | Code Editor library

currently the Repository API of Vorto 0.11 does not support to import models via REST. It is a pure read-only REST API. You can "only" import models via the Repository Web Interface (https://vorto.eclipse.org)

However there is a GitHub issue about your request: https://github.com/eclipse/vorto/issues/1667 and it will be available in 0.12 Release, which is planned for end of august.

The Vorto Importer Plugin API is an API to implement an Importer Plugin that you can register with the Vorto Repository. An Importer plugin could for example be a Web Of Things or JSON Schema Plugin, that converts these 3rd party descriptors to Vorto Information Models. As I understand your question, that is not what you wanna do :)

I created an issue for you request to support this in the Javascript converters: https://github.com/eclipse/vorto/issues/2029

As stated in the issue, as a current workaround, you can register your own custom converter function with Java and re-use this function across your mappings. In these java converter functions, you have all the power of the java language to convert to extract the right property from the arbitrary list. In order to find out how to implement your own custom converter function with Java, take a look here: https://github.com/eclipse/vorto/tree/master/mapping-engine#Advanced-Usage

TL;DR

To resolve your issue, store your OAUth credentials as environmental variables.

E.g. in debian et al., export BOSCH_CLIENT_ID=... etc., then start the dashboard in the same terminal.

Context

I was about to ask the same question, as I got the same error message no matter how I referenced the config.json file (relative path, absolute path, no reference, etc.).

For clarification, the tutorial pointing to a config.json resource for storing OAuth credentials is here.

Quoting:

While the dependencies are being installed, create the config.json file and insert client_id, secret and scope from your Already created OAuth2 Client. The content of the file has to look like this:

{ "client_id": "", "client_secret": "", "intervalMS": 10000 }

The reference to the config.json file has been removed from the README.md resource in the vorto-dashboard module of vorto-examples.

The latest README.md suggests providing the OAuth credentials through environmental variables:

You can provide your OAuth2 credentials through environment variables. The three environment variables you have to provide are:

BOSCH_CLIENT_ID

BOSCH_CLIENT_SECRET

BOSCH_SCOPE

[...]

Looking at the source, I can only find an explicit reference to a config.json in the start script entry for package_for_deployment.json (nor anything around the source seems to be consuming, say, argv[2] for that matter).

The AuthToken.js resource in charge of handling OAuth credentials only seems to reference environmental variables through the process.env.[...] references.

Elaboration

This is only speculation at the time of writing, but I suspect the reason why the config.json methodology has been abandoned might have something to do with strengthening security, i.e. not storing OAuth credentials permanently in a file.

If that much is true, then the tutorial page should probably be amended with the latest instructions from the README.md.

Quite a late answer. It's very likely, if you installed the package through Umbraco Package Manager and not through NuGet, the @using might not work in class files, but only in views.

Therefore, you have to also install the package through NuGet, that should make the @using valid in the class files.

The buffer shows you a lot of escape sequences, like [1m[33msyj[39m[0m[38;5;242m@[1m[36m. Try to get rid of them in your prompt; the Tramp manual explains some techniques.