Decouple Configuration Language

[erikreinert]

Overview

After getting our first pipeline to run in GitHub Actions (https://github.com/ALT-F4-LLC/vorpal-sdk/actions/runs/10126896725/job/28004044745 - yay) there was a moment of realization that if you are using a compiled language (Go, Rust, etc) that you will need to compile your Vorpal code to run Vorpal. This was a known limitation however, it was still included to allow the project to go as far as it could with that.

Now that we have hit kind of a hard wall, it may be valuable to decouple the language to configure packages in from the language we build Vorpal in. Because we use GRPC, we will still need to translate ?? -> GRPC schemas but we can use that middle man language as the configuration interface.

Requirements

1. Type System
   2a. Modularity (remotely downloadable is a plus)
   2b. Functional
2. Easily Expressible (flattening, currying, etc)

Embedded Languages

There is the possibility of using a embedded language that works naturally with Rust that we could then import into the language and parse. This would be nice because then we could just inject the file directly into Rust language and build.

Investigate

• Cue
• DHall
• KCL
• Lua
• Nickel