diff --git a/docs/technical-documentation/solution/tools/Backstage/CNOE-backstage-commit-history/_index.md b/docs/technical-documentation/solution/tools/Backstage/CNOE-backstage-commit-history/_index.md index 1cddb6d..d9c820a 100644 --- a/docs/technical-documentation/solution/tools/Backstage/CNOE-backstage-commit-history/_index.md +++ b/docs/technical-documentation/solution/tools/Backstage/CNOE-backstage-commit-history/_index.md @@ -1,11 +1,11 @@ ## CNOE Bacstage commit history This page describes the features and changes added to CNOE Backstage, along with a brief summary of what was done in each commit. -Commits and changes that are important for implementation of the EDP Backstage will be marked with red color and commits -that could be interesting for EDP Backstage but not in priority will be marked with yellow color. Commits are listed from newest to oldest. +Commits and changes that are important for implementation of the EDP Backstage will be marked with red color and commits +that may be relevant, but not in priority, will be marked with green color. Commits are listed from newest to oldest. -### №19. Commit name: Imported roadiehq http request plugin +### №19. Commit name: Imported roadiehq http request plugin [Link to a commit](https://github.com/cnoe-io/backstage-app/commit/135c0cb26f3e004a27a11edb6a4779035aff9805)
This commit adds the `@roadiehq/scaffolder-backend-module-http-request` plugin. This plugin provides Scaffolder actions that allow sending web requests within Backstage templates. @@ -32,7 +32,7 @@ backend.add( This integrates the module into the Backstage backend. -This commit introduces functionality that may be useful for extending our Backstage templates with web request capabilities +This commit introduces functionality that may be useful for extending our Backstage templates with web request capabilities ### №18. Commit name: add mkdoc to docker image [Link to a commit](https://github.com/cnoe-io/backstage-app/commit/9232d633b2698fffa6d0a73b715e06640d170162)
@@ -52,7 +52,7 @@ This commit is mostly refactoring 2. Reformatted and standardized code style -### №15. Commit name: Extended plugin to support more k8s objects +### №15. Commit name: Extended plugin to support more k8s objects [Link to a commit](https://github.com/cnoe-io/backstage-app/commit/2cde0a09caf55fe907463b0b8b4a6321482b322e)
This commit contains improvements to the plugin for working with k8s. All changes are in file `packages/backend/src/plugins/k8s-apply.ts` #### Changes: @@ -113,7 +113,7 @@ The name of this commit is misleading because, in addition to updating the Backs [Link to a commit](https://github.com/cnoe-io/backstage-app/commit/b8e4f08914af17a48ed6b8b83a3621a9f4b4181d)
In this commit only README was updated -### №6. Commit name: use cnoe theme +### №6. Commit name: use cnoe theme [Link to a commit](https://github.com/cnoe-io/backstage-app/commit/12eef8100d2521a6f665ef603ebe8196b12c8e96)
In this commit design of user interface was updated and integrated into the Backstage app @@ -122,7 +122,7 @@ In this commit design of user interface was updated and integrated into the Back 2. UI style is connected to Backstage in file `packages/app/src/App.tsx` 3. Routs to CNOE logo for interface are created in file `packages/app/src/components/Root/Root.tsx` - This commit could be intersting for the team, because here we can see how to connect custom ui to backstage and how to remove CNOE logo + This commit could be intersting for the team, because here we can see how to connect custom ui to backstage and how to remove CNOE logo ### №5. Commit name: Add workflow to automate backstage builds [Link to a commit](https://github.com/cnoe-io/backstage-app/commit/9ee3514e51c1a354b7fe85a90117faf8328bfa0b)
@@ -144,7 +144,7 @@ In this commit were added github workflow for building backstage image and Docke 1. Created custom CNOE plugin for integration with apache-spark (`/plugins/appache-spark`) 2. Created custom CNOE plugin for integration with apache-spark (`/plugins/argo-workflows`) 3. Created custom CNOE plugin for integration with apache-spark (`/plugins/cnoe-ui`) -4. In Backstage backend in file with custom gitea actions ( packages/backend/src/plugins/gitea-actions.ts ) were commented out: checkGiteaContentUrl, checkDurationLimit and checkAvailabilityGiteaRepository +4. In Backstage backend in file with custom gitea actions ( packages/backend/src/plugins/gitea-actions.ts ) were commented out: checkGiteaContentUrl, checkDurationLimit and checkAvailabilityGiteaRepository 5. Integration with ArgoCD was added into backend of the Backstage as a backend plugin ( packages/backend/src/plugins/argocd.ts) 6. In `packages/app/src/App.tsx` `argo-workflows plugin` and `apache-spark` plugin were integrated into Backstage and routs for their pages were created 7. To the backstage component for the catalog items (`packages/app/src/components/catalog/EntityPage.tsx`) were integrated components from `argo-wrkflows` plugin.
And was added component EntityArgoCDOverviewCard from @roadiehq/backstage-plugin-argo-cd which is a visual component for showing ArgoCD status of the catalog items, which are registered in ArgoCD. [Link to plugin's repo](https://github.com/RoadieHQ/roadie-backstage-plugins/tree/main/plugins/frontend/backstage-plugin-argo-cd).