You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some information in the Enarx.toml is exposed to the host when running in enarx. The host should have a right to view this before actually executing a workload. This would make enarx/enarx#2148 redundant.
In a client side application using Enarx the application could ask the user if they would like to grant those resources to a workload.
In a server side application an error could be displayed to an administrator that resources requested in the Enarx.toml will not be available, must be reconfigured, etc.
Returning an Enarx.toml with any possible secret data removed or marked as Unknown might be a nice way to implement this.
If packages are ever encrypted on the server side then this must be provided in a Resources.toml or something which is not encrypted.
The text was updated successfully, but these errors were encountered:
Some information in the Enarx.toml is exposed to the host when running in enarx. The host should have a right to view this before actually executing a workload. This would make enarx/enarx#2148 redundant.
In a client side application using Enarx the application could ask the user if they would like to grant those resources to a workload.
In a server side application an error could be displayed to an administrator that resources requested in the Enarx.toml will not be available, must be reconfigured, etc.
Returning an Enarx.toml with any possible secret data removed or marked as
Unknown
might be a nice way to implement this.If packages are ever encrypted on the server side then this must be provided in a
Resources.toml
or something which is not encrypted.The text was updated successfully, but these errors were encountered: