Skip to content

Implement ELASTIC wasi-security - #277

Open
Michielvk wants to merge 3 commits into
absmach:mainfrom
idlab-discover:feat/wasi-security
Open

Implement ELASTIC wasi-security#277
Michielvk wants to merge 3 commits into
absmach:mainfrom
idlab-discover:feat/wasi-security

Conversation

@Michielvk

Copy link
Copy Markdown
Contributor

What type of PR is this?

New feature as part of the ELASTIC project. As discussed and agreed upon by all partners during the technical meeting in Belgrade.

What does this do?

This PR allows a user to supply an additional config file to the Proplet. The Proplet parses this config file and configures Wasmtime accordingly.

Have you included tests for your changes?

Yes. All pass.

Did you document any new/modified features?

Yes. And an example config file is available.

@rodneyosodo

Copy link
Copy Markdown
Contributor

@Michielvk, can we use Metadata rather than having a new entry on the task?

@Michielvk

Michielvk commented Aug 19, 2026

Copy link
Copy Markdown
Contributor Author

@Michielvk, can we use Metadata rather than having a new entry on the task?

@rodneyosodo, this was the original plan, but it turns out that the Metadata field is only used by the Manager and stripped while creating the startPayload before sending it to the Proplet.

https://github.com/idlab-discover/propeller/blob/6d32fa570e9f40da0d499ebf0095be2f6e125549/manager/service.go#L2041-L2042

Since we need these additional configs in the Proplet to configure Wasmtime, we decided during the Belgrade meeting to add a new field instead that is intended to supply custom config to the Proplet directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants