Extensions: Phases

[KlapTrap]

Most of the below work will revolve around the frontend extensions and is all subject to change.

Phase 0 - Initial work 🌞 DONE

Laying the groundwork for all future work. This is mainly focusing on the FE extensions. Work done; #2133 #3140 #3048 #2962 #2950 #2948

Phase 1 - Reorganising the project 💥DONE

Begin work to convert the frontend code into a monorepo. This phase is mainly concerned with getting the project structure correct but still allowing imports across packages. Work done here #3173.

Phase 2 - True monorepo ✨WIP

Decouple the packages, ensure there are no cross package imports. Provide a public api for each packages and internally referencing the other packages via the packages package.json.

See https://github.com/cloudfoundry-incubator/stratos/labels/extension-phase-2.

Decouple the store from the cf module

• Entity catalogue - Done
• Entity pipeline - Done
• Document how to use entity catalogue and pipelines - Not started
• Where reasonable, ensure the CF module is following best practices with the new store layout e.g. using action builder, using action configs and the new api pipeline.
• Additional issues found along the way.
• DEFINITION OF DONE: when the application is working as it does in v2-master.

Related issues: https://github.com/cloudfoundry-incubator/stratos/issues?q=is%3Aissue+is%3Aopen+label%3Aextensions-store

Move CF Components and services into cf module.

• Mostly done, there are some none CF components that reference CF and need to to tidied up.

Related issues: https://github.com/cloudfoundry-incubator/stratos/issues?q=is%3Aissue+is%3Aopen+label%3Aextension-cf-components

Allow the frontend permissions framework to be extended - Not started.

Phase 3 - Begin providing a sandbox 😎 - WIP

Ensure we can start developing an extension outside of the stratos repo only referencing the Stratos packages via a package.json (local references at first). Create good docs outline what to do - keep the docs updated!!

See https://github.com/cloudfoundry-incubator/stratos/labels/extension-phase-3

Phase 4 - Stratos core NPM packages 📦

Publish npm packages and test with the work from the previous phase.

Phase 5 - Hosting extensions within their own repo ⛳️

How do we manage Stratos and extensions versioning? How do we CI these changes and ensure we don't break things? How to we notify users that an extension in incompatible with their installed version of Stratos?

Phase 6 - Allow stratos users to install an extension from a git repo 🙌

Using package.json and npm?
TODO: Flesh this out.

[nwmac]

This is out of date - will update with the new plan