-
Story
-
Resolution: Done
-
Minor
-
None
-
None
-
False
-
-
False
-
Unset
-
None
-
-
The entity provider can be challenging to work on. Additionally it does not have full test coverage. The goal of this ticket is to review the Entity Provider, see if there are ways to simplify its development, improve its test coverage, and make it easier to build and deploy.
Definition of done:
- Entity Provider is reviewed
- Plan is created that lays out what, if anything we should do including refactoring, testing gaps, CI/CD opportunities, etc and cards open as work items.
Note: An area worth exploring may be to see if the entity provider library and the plugin may be merged into a single project. For historical reasons the logic is in the library and the plugin is a thin wrapper around that. This makes it harder to work on and develop as one needs both on their system and must do things with local NPM deps, which can be difficult to deal with. It may be worth investigating merging the two and then determine how to do proper integration testing with RHDH / backstage.
1.
|
Move lib code into ep |
|
Closed | |
Adam Drew |
2.
|
Create a backstage monorepo and move EP code in |
|
Closed | |
Adam Drew |
3.
|
Create new gitlab project and push code up |
|
Closed | |
Adam Drew |
4.
|
Reconfigure e2e and unit test gitlab actions |
|
Closed | |
Adam Drew |
5.
|
Create a build and publish it to Stage |
|
Closed | |
Adam Drew |
6.
|
Retire old gitlab projects |
|
Backlog | |
Adam Drew |
7.
|
Deprecate old repos |
|
Closed | |
Adam Drew |