Skip to content

Split Package and Terraform registry codebase

Embracing the value of iteration we built the Terraform Registry by leveraging the Package Registry app. This allowed us to re-use most of the existing logic.

In time the two needs to separate so that the dependencies of the two are not a blocker for further development. All the registries will still share the similar look and feel, and that is planned by leveraging a set of (already existing) shared UI components (currently located in vue_shared/components/registry)

This suit of components probably needs to be extended.

This issue aims to be the single source of truth for all the conversation around the effort of splitting the two registries, what approaches and step we need to take and how to efficiently iterate on them.

A draft of a plan

  1. Identify all the components present in the Package Registry that we can efficiently recycle
  2. Detach the component identified at the previous step, generalize them and move them over to the shared folder
  3. Swap the 'core' app for the Terraform List page with a new dedicated one, wire shared components
  4. Swap the 'core' app for the Terraform Details page with a new dedicated on, wire the shared components

For the last two points we may need a feature flag.