-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[North] Add POST, PUT HTTP requests North #962
Comments
Ok for this improvement. let us know if you need support. I look forward to review your PR. We just need to make sure about the overlap with OIConnect (which we may only reserve for the OIBus to OIBus communication) |
Just a little comment to let you know that I am going to start this feature today or the next week. |
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
burgerni10
pushed a commit
that referenced
this issue
Jan 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With Atipik-solutions, we want to import production order data (OF) from the client's IT to WATSY's one. These OFs are stored in the customer database. The "FolderScanner" South and "SQLRequest" South handle part of this transfer thanks to the file's transfer to a North. It therefore remains the transfer to another IS
For this new North, be able to convert the data from the csv files into HTTP requests (PUT, POST ....) to an API with a body created in this North. is the aim. For this, the North layer aims to make a mapping of the fields present in the csv file with the name of the fields to be set up in the body of the request. For example, transform the field present "id" from the csv into a field named 'id_OF' in the request's body.
For the front-end, the first part is the authentication one. There are the parameters for the requests (token or credentials) as well as the host-name to send requests ("https://example.com/") . A second part allowing the configuration of the mapping. This one will be able to offer mandatories predefined fields but also a drop-down list of other predefined or not fields. Finally, we will find basic sections allowing the choice/definition proxy, the caching and the South subscription.
This issue comes from the mail I've sent to @jfhenon and @burgerni10.
The text was updated successfully, but these errors were encountered: