Skip to content
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

Shell Manager - Execute and run gadgets #159

Open
Tracked by #152
shekohex opened this issue May 22, 2024 · 1 comment
Open
Tracked by #152

Shell Manager - Execute and run gadgets #159

shekohex opened this issue May 22, 2024 · 1 comment
Assignees

Comments

@shekohex
Copy link
Contributor

shekohex commented May 22, 2024

After downloading the blueprint #158 it should be ready to be executed, each blueprint would expect to be executed with a set of env variables that are set by the manager for the child process (or remote process):

  1. RPC_URL: The remote RPC url for tangle
  2. KEYSTORE_URI: the keystore file where the keys are stored and could be retrieved.
  3. DATA_DIR: is an isolated path for where this gadget should store its data (database, secrets, …etc)
  4. BLUEPRINT_ID: the active blueprint ID for this gadget
  5. SERVICE_ID: the active service ID for this gadget
  6. HEALTHCHECK: If set, the gadget just prints its version and exist with a status code zero, to check if the binary is configured correctly.

Once it starts, the child process or the remote process should be kept alive, and monitored by the shell manager. If it fails or panicked, the shell manager should report the issue to the operator and depends on the configuration, the gadget may need to be restarted again.

@shekohex
Copy link
Contributor Author

For keystore URI: :mem:, or file://... and kms://...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Not Started 🕧
Development

No branches or pull requests

2 participants