You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VSS files to be copied to new repo, folder called vss-json
Databroker JWT copied to new repo, folder called jwt. This is based on the assumption that in the long run (> 3 years) we will either not have KUKSA Server any longer, or it should have migrated to the tokens currently used by Databroker
Step 2: Remove files from kuksa.val and add kuksa-common as submodule
Remove all files copied
Add kuksa-common as submodule on top level.
Adapt build scripts to either use files from the submodule or alternatively use other mechanism like separate clone
Acceptance criteria: Tools works as before
Discussion points
We have previously discussed removing certs/tokens from default installations, but that seems like a lengthy process so maybe best to first just migrate everything
An alternative approach would be to just copy, not remove, and wait with migration until the corresponding components are migrated, but that will make migration somewhat more complex, then there is a risk that certs are just copied.
Background
We have said that we want to split this repo into multiple repos in eclipse-kuksa. As part of https://github.com/eclipse/kuksa.val/wiki/Proposal-for-splitting-of-KUKSA.val it is proposed to create a repo kuksa-common where data typically needed by multiple applications are stored. This issue intends to propose a way forward
Step 1: Copy files to new repo
vss-json
jwt
. This is based on the assumption that in the long run (> 3 years) we will either not have KUKSA Server any longer, or it should have migrated to the tokens currently used by Databrokertls
jwt/server
jwt
proto/kuksa
proto/sdv
Step 2: Remove files from kuksa.val and add kuksa-common as submodule
Discussion points
The text was updated successfully, but these errors were encountered: