Lucas Servén Marín

Sounds great, I'd love to see Observatorium formalize its development process more. To add some historical context, the project already published a few releases in semver format up to 0.1.2....

yes totally :+1:

> Versioning the spec in the same way as the API itself would be nice Hmm I tend to disagree here. The HTTP API is a contract and the version...

Configuring rbac in OpenShift doesn't change at all, but you mean how to configure the API to use the OpenShift authentication server for OIDC?

Yes. We also need to think carefully about ensuring that the paths that the HTTP API exposes actually conform to the version of the API contract, e.g. the Rules API...

@leifmadsen This project is completely agnostic to OpenShift and even to Kubernetes; it knows nothing about any underlying scheduler or orchestration. The tenants file is simply a mapping of organization...

I think that by calling it legacy it is already effectively deprecated, no? I would be in favor of dropping it from main and cutting a new release soon.

Hi @letttung, you can use the `ENDPOINT` environment variable [0] to control this. FWIW, I have this working with Scaleway's S3-compatible service. [0] https://github.com/cloudposse/goofys/blob/6a7a1647ef4ffd576530ddbe76eb7026a406a46e/rootfs/usr/bin/run.sh#L7

Looks like doc checks are failing because the V2 branch of https://github.com/grpc-ecosystem/go-grpc-middleware no longer exists

While working on automating deployments for fal apps, I found that having all of the app's metadata was also really useful. This allows us to automate not just the deployment...