Draft: Server side scripting

Summary

Related to #108

Focus

Point the reviewer to the core of the code change. Where should they start reading? What should they focus on (e.g. security, performance, maintainability, user-friendliness, compliance with the specs, finding more corner cases, concrete questions)?

Test Environment

How to set up a test environment for manual testing?

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

include/linkahead/scripting.h

+/*
+ * This file is a part of the LinkAhead Project.
+ * Copyright (C) 2025 Joscha Schmiedt <joscha@schmiedt.dev>
+ * Copyright (C) 2025 IndiScale GmbH <info@indiscale.com>
+ *
+ * This program is free software: you can redistribute it and/or modify
+ * it under the terms of the GNU Affero General Public License as
+ * published by the Free Software Foundation, either version 3 of the
+ * License, or (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ * GNU Affero General Public License for more details.
+ *
+ * You should have received a copy of the GNU Affero General Public License
+ * along with this program. If not, see <https://www.gnu.org/licenses/>.
+ *
+ */
+#pragma once
+
+#include "caosdb/scripting/v1alpha1/main.pb.h"
+#include "caosdb/scripting/v1alpha1/main.grpc.pb.h"
+#include <string>
+#include <vector>
+
+#include <grpcpp/grpcpp.h>
+
+namespace linkahead::scripting {
+using namespace caosdb::scripting::v1alpha1;
+
+ExecuteServerSideScriptRequest construct_execute_server_side_script_request(
+  const std::string &script_name, const std::vector<std::string> &positional_arguments,
+  const std::vector<NamedArgument> &named_arguments, const std::vector<std::string> &script_files,
+  const std::string &auth_token, int timout_ms = 0, bool run_async = false);
+
+ExecuteServerSideScriptResponse
+call_server_side_script(const std::shared_ptr<grpc::Channel> &channel,
+                        const ExecuteServerSideScriptRequest &request);
+
+} // namespace linkahead::scripting
\ No newline at end of file