cleaned up walnut and shrink the features for now so i can work on it…

… from time to time
Kruemelmann · May 22, 2023 · 427781c · 427781c
1 parent 0e4d5a7
commit 427781c
Show file tree

Hide file tree

Showing 86 changed files with 308 additions and 23,156 deletions.
diff --git a/db/postgres/init.sql b/db/postgres/init.sql
diff --git a/docker-compose.dev.yml b/docker-compose.dev.yml
diff --git a/docs/README.md b/docs/README.md
@@ -14,7 +14,5 @@
 
 ## Authentication
 
-* [Overview](./authentication/README.md)
 * [Token](./authentication/Token.md)
 * [Internal](./authentication/Internal.md)
-* [LDAP](./authentication/LDAP.md)
diff --git a/docs/authentication/LDAP.md b/docs/authentication/LDAP.md
diff --git a/docs/authentication/README.md b/docs/authentication/README.md
diff --git a/docs/authentication/Token.md b/docs/authentication/Token.md
@@ -4,4 +4,4 @@
 
 - to use the remote cache/execution of walnut you need to pass a token to walnut. This token is send via header in the cli call of bazel.
 
-TODO
+TODO implmenet this as soon as i get to remote execution
diff --git a/docs/db/schema/design.md b/docs/db/schema/design.md
diff --git a/docs/db/schema/screenshot.png b/docs/db/schema/screenshot.png
diff --git a/docs/modules/README.md b/docs/modules/README.md
@@ -5,26 +5,12 @@ This chapter will explain how walnut store modules.
 ## Kind of Modules
 
 * local
-* linked
-* mirrored
+* cached
 
 ### local-Modules
 
 Local modules are stored inside the volume of the walnut-store service.
-If walnut runs inside docker using docker-compose this volume is mapped onto the local filesystem.
-Inside kubernetes walnut can store the local modules in several different ways. [kubernetes volume](https://kubernetes.io/docs/concepts/storage/volumes/)
-
-
-### linked-Modules
-
-Linked modules are not stored inside walnut.
-They are only referenced by a url inside the walnutdb.
-If a build request them the store service tries to load the modules from the url.
-An error is send if the module can not be loaded, the errors are explained inside the errors chapter of the walnut docs.
-Linked Modules can ether be the url to a http-based index-registry or a publicly available fileserver.
-
-### mirrored-Modules
-
-Mirrored modules are modules that are loaded initialy when they are requested, later if they are requested walnut checks the original url for a newer version of the module and if it finds them they are getting downloaded to walnut as well.
 
+### cached-Modules
 
+TODO implement later. this option will look into a public modules store and try to load it + the specified version into walnut.
diff --git a/pb/walnut.proto b/pb/walnut.proto
diff --git a/protos/walnut.proto b/protos/walnut.proto
@@ -0,0 +1,25 @@
+syntax = "proto3";
+
+package walnut;
+
+// this are the 3 roles that a client can have
+enum Role {
+  ADMIN = 0; // can add and delete modules
+  USER = 1;  // can start builds
+  VIEWER = 2; // can only download roles but not execute remote builds
+}
+
+// ---- Auth service ---
+service AuthService {
+  rpc Login(LoginRequest) returns (LoginResponse) {}
+}
+
+message LoginRequest {
+  string username = 1;
+  string password = 2;
+}
+
+message LoginResponse {
+  bool successful = 1;
+  string token = 2;
+}
diff --git a/src/web/static/ui/src/assets/.gitkeep → src/auth/.gitkeep b/src/web/static/ui/src/assets/.gitkeep → src/auth/.gitkeep
diff --git a/src/auth/authserver.go b/src/auth/authserver.go
diff --git a/src/auth/genproto.sh b/src/auth/genproto.sh
Original file line number	Diff line number	Diff line change
Expand Up		@@ -4,4 +4,4 @@

		- to use the remote cache/execution of walnut you need to pass a token to walnut. This token is send via header in the cli call of bazel.

		TODO
		TODO implmenet this as soon as i get to remote execution