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

[TASK] Blueprint must specify deployment target #412

Open
drewstone opened this issue Oct 28, 2024 · 2 comments
Open

[TASK] Blueprint must specify deployment target #412

drewstone opened this issue Oct 28, 2024 · 2 comments
Assignees

Comments

@drewstone
Copy link
Contributor

Overview

Currently I don't know where we are specifying whether a blueprint gadget/instance is meant to be run natively, from docker, or from another target environment. This task should implement this as well as add support for the deployment targets supported in the blueprint manager.

@drewstone
Copy link
Contributor Author

We could consider putting it directly in the main?

  • #[sdk::main(env, DockerDeployment)], #[sdk::main(env, NativeDeployment)], #[sdk::main(env, SgxDeployment)]
  • We could add it to the TOML, as part of the blueprint creation CLI flow? `cargo tangle blueprint create --name <...> --target <...>
  • Feedback @tbraun96 @shekohex @Serial-ATA

@shekohex
Copy link
Contributor

shekohex commented Oct 28, 2024

It's currently declared in your Cargo.toml. that's when you build your blueprint it will be generated in your blueprint.json file.

I will expand more on that and give an example.

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

No branches or pull requests

4 participants