1d1f01389c
## Description > TL;DR: Separating the DatasourceConfiguration as a new collection to accommodate for environments This PR adds services and models for DatasourceConfigurationStorage, which will now hold the datasourceConfiguration previously held in Datasource. Additionally, DatasourceConfigurationStorage will also hold invalids and messages from the datasource. It's indexed on datasourceId and environmentId. This PR doesn't change the way Datasource consumes and keeps datasourceConfiguration. This will be followed by other PR which will change consumption of datasourceConfiguration into a transitory field ### Changes Made: - Created DatasourceConfigurationStorage model with datasourceId, environmentId, datasourceConfiguration, invalids, and messages fields. - Created DatasourceConfigurationStorageRepository interface and implementation for managing DatasourceConfigurationStorage in the database. - Added DatasourceConfigurationStorageService for performing CRUD operations on DatasourceConfigurationStorage. - TODO : Update DatasourceService to use DatasourceConfigurationStorageService for managing DatasourceConfigurationStorage. #### PR fixes following issue(s) Fixes https://github.com/appsmithorg/appsmith-ee/issues/1339 #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [ ] Jest - [ ] Cypress ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Test-plan-implementation#speedbreaker-features-to-consider-for-every-change) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans/_edit#areas-of-interest) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed |
||
|---|---|---|
| .. | ||
| .yarn | ||
| client | ||
| rts | ||
| server | ||
| shared | ||
| util | ||
| .eslintrc.base.json | ||
| .gitignore | ||
| .yarnrc.yml | ||
| package.json | ||
| yarn.lock | ||