-
Follow up to #192618
Register versioned CRUD (Create, Read, Update, Delete) + List public API routes for Dashboards using the v3 content management schema.
API path names, path parameters, and req…
-
Prior to making the Dashboards Public API available, we should decide on how best to organize the base URL path for the CRUD routes.
Two suggested base paths are
1. `/api/dashboards`
2. `/api/dashboa…
-
Nesting the patient, dr and medifles table into the user resources in routes will allow crud capabilities in the user admin account to be able to create new patient, dr and medifile templates/files fr…
-
Here are the routes we currently have for a CrudController that uses the common operations:
So it's basically
| Operation | HTTP Verb | URL |
| ------------- | ------------- | ------------- …
-
We'll need to update CRUD routes so that we have the following views:
- "view my escapes" where the user is looking only at itineraries that they have submitted to the database
- "browse escapes" …
-
Create public CRUD routes for Maps and add validation (parts of Dashboards-as-code project)
-
change the title of the app to "CRUD Application for XYZ Company".
-
Creation of Beer CRUD routes.
-
All issues concerning note creation, reading, updates and deletions
-
In https://github.com/elastic/kibana/pull/194677 we enabled native roles in FTR configs by default for Search and Observability projects. We had to skip existing "old" tests, that were validating role…