formalize manifest into an standard (vs a low code tool)

[earizon]

This project rocks and is ideal in many scenarios.

As I see it, just formalizing it as an standard that different impletations can transform into running code, could represent a boost to the project.

Many teams can be reluctant to abandon Java or Go or C# or ... for many reasons (security, expertise, ...), but I guess they all would like to have the simplicity of manifest in their dev stack.

By just putting some effort to create a formal definition for the "manifest" standard, and leaving the current implementation as a default reference for the standard, many other "workgroups" could be attracted.

I'm talking (dreaming actually) of a Cloud Native Foundation alternative golang/rust implementation preinstalled in future Kubernetes, docker, AWS/GCP/Azure/...

From my point of view manifest suits perfectly the "desired future state" deployment of modern cloud stacks. A little standarization is all that needed.

My two cents!

[brunobuddy]

Hello @earizon

Thanks for you comment. I can see the point, but do you have similar "standards" in mind ? Things that have many implementations in different languages ?

The thing is that with Manifest, our main goal is to make people's life easier, we want to make deploying a backend smooth and accessible. The choice of using YAML goes it that direction, no need to be an expert in any language to leverage Manifest's power. What would be the purpose of making it a standard in your opinion ?

[earizon]

Yes, actually I was thinking for example of standards like OpenAPI. The API is defined also as a yaml, then different tools can generate dynamic documentation or even client/server code. (https://openapi.tools/)

Other "blur" example could be Kubernetes Gateway API, offering a "yaml" standard to different API Gateways (Envoy, Traeffic, Kong, AWS/Azure/GCP/...).

The purpose could be to bring attention from other "working groups", maybe to add support to the standard for some async message queue, quite typical in modern interactive apps.

My comments are obviously just a "point of view", not even a "feature request".

Thanks again for the project!