-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(service): automate csv assignment inside enclave.json #45
Comments
I would like to work on this issue, please assign this issue to me under GSSoC'23. |
Hey, @harshsingh32 assigning this issue to you. Please rename the new branch to |
Hey @harshsingh32, any updates? |
hello @qascade, I wd like to work on it. |
@prakrit55 Assigning this to you. |
hey @qascade, do I need to create yaml files to automate the task ? |
No, currently we are embedding temp_enclave.json and copying it on the go app just before compilation. Currently we are using CSV files to take input tables, but the file paths has to be mentioned before hand inside the enclave.json in files field. Otherwise service run fails. I want you to automate the csv filling inside the json to be automatic. You need to pick the csv filenames from source.yaml of Collaborators itself. |
ohh, then where can I find the yamls ? |
In samples folder |
Description
CSVs can't be moved inside enclaves unless explicitly mentioned inside the enclave.json. Check
files
field inservice/temp_enclave.json
. I want that to be automated and to be picked from Yaml, not through temporary CSV's.The enclave.json is to created/modified before ego-sign using sources specified in yaml.
How are you planning to resolve this issue?
One of the following strategies may be used. You are free to create you own strategy as well.
The text was updated successfully, but these errors were encountered: