search

lsc-sde / lsc-sde

Lancashire and South Cumbria Secure Data Environment
MIT License
1 stars 0 forks source link

Submodule Restructure #62

Open qcaas-nhs-sjt opened 1 month ago

qcaas-nhs-sjt commented 1 month ago

As a developer I would like the primary repository to be structured in a way that makes it easier to find what you're looking for.

At present the primary repository is organised as Type (iac/docker/other) then by programming language, then by product. This makes it harder to find the repository you want. Instead it might be prefereable to organise by product type, product and purpose:

So something like this might be more appropriate:

|- supporting-products
   |- cert-manager
       |- flux
   |- nginx
       |- flux
   |- keda
      |- flux
   |- guacamole
      |- flux
      |- helm
      |- client
|- sde-products
   |- analytics-workspace-management
       |- flux
       |- helm
       |- management-portal
       |- python module
       |- java library
   |- aks-dns-operator
       |- operator
       |- flux
       |- helm
   |- secrets-distributor
       |- operator
       |- flux
       |- helm
   |- provisioning
       |- terraform
          |- azure
          |- aws
          |- gcp
          |- kubernetes
       |- flux
       |- helm
|- 3rd-party-products
   |- jupyterhub
       |- flux
       |- hub image
   |- jupyter-notebooks
       |- datascience-notebook
       |- datascience-notebook-slim
   |- ohdsi
       |- flux
       |- helm
       |- web-api

46

qcaas-nhs-sjt commented 1 month ago

@vvcb @m1p1h Have put this in as technical debt, I've suggested a different way of structuring the submodule directory structure which will hopefully make it easier to find things, and hopefully make it less confusing. I'm not set on it but am happy if anyone has any other ideas on how to structure it. Thoughts appreciated.