Create functionality to import single API backend configuration

[bajiat]

Based on task #323, create functionality to import single API backend configuration.

Definition of done

• Create user interface button to upload single API backend configuration.
• Create function to parse uploaded to configuration to JSON object.
• Create function to insert configuration into API backends collection in the database.
• Make sure API backend is validated against API backend schema.
• After upload, re-direct user to the API configuration form for the uploaded API.

[frenchbread]

Related PR - #344. Mainly the task is done. Still need to figure out how to get dynamic path value in both/collections/backendConfigurations.js file so that we are not providing hard-coded path which probably won't work on other PC's. @brylie, Any ideas?

[brylie]

@frenchbread, try using GridFS, which stores the files in a collection. We already have GridFS in our project.

[frenchbread]

Wireframe:

[frenchbread]

PR #344 created. Please review.

Followed wire-frame that is provided above, kind of rewrote api config file import approach.
Changes:

• most of the checks and parsing is done on client-side (so it is much faster)
• 2-panel view (file upload drop box and file preview (with syntax highlights))
• only YAML and JSON config files are allowed for now
• once submit button is clicked - form contents are sent to server where final schema verification takes place
• error handling provided almost everywhere where possible - so pretty secure
• added custom parsing of required fields
• couple of tips on "How to import configs" are provided.

[brylie]

Looks good. Also keep in mind the redirect after success, as this will help orient the user to the result of their action.

[frenchbread]

@brylie Ok. Once api backend view page is ready & merged, I will add functionality to redirect after import.

[brylie]

@frenchbread cool. The pull request has been submitted and updated.

[frenchbread]

@brylie Updated PR #344 with redirect to view page. It shows 404 for now because #390 is not in develop yet.

I've made a small suggestion in #390 to use simpler path for api backend view in url. If it will be accepted I will need to change the redirect path in this PR as well.