Namya LG

Yes, I think that can be achieved The endpoint `/gcbm/upload/:option` will be able to handle both the cases 1. `/gcbm/upload/local_path` (which means reference a mounted volume/or local path, as an...

In my understanding, `/path` : create a directory if not existent, this will house the input folders (currently the input folder is expected to have `layers`, `input_database` and `config`) `/check`...

Yes, I have destroyed the resources Do I have to follow method 1 or 2 ?

okay, I'll try it again The resources allocated are - Storage - Pub/Sub - service account Am I missing anything ?

I'm unable to identify which resources these point to ``` Error: Error creating Service: googleapi: Error 409: Resource 'fc-ingress' already exists. │ │ with google_cloud_run_service.fc-ingress, │ on main.tf line 133,...

I have ensured the storage bucket `simulation_data_flint-cloud`, pub-sub resources `small-simulations` and `large-simulations`, and the service account `flint-cloud-sa` are deleted, but still face the same error.

Alright. Are you referring to @iamrajiv 's [fork ](https://github.com/iamrajiv/FLINT.Cloud) ?

Okay 👍🏻

> Maybe, in the future, we can have a function run when the server starts which will construct these instances again depending on the files stored from the previous uploads....

How exactly will the `compare-json` functionality be generalised ? For these set of inputs, we have the required configuration to compare against, but what if the user has a different...