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
Is your feature request related to a problem? Please describe.
In lieu #279, we should have a way that we can see what resource will be accessed and which components will access those resources. Additionally a whitelist functionality for resources should be available so components can be restricted to which resources they have access even if they are somehow given access accidentally.
Propose a solution wick run app.wick --dry-run should load the application but not actually run the application but simply report on the list of all of the resources that are used by the application and which components access them.
wick run app.wick --enforce whitelist.wick should attempt to run the application but compare all of the resources to the resource whitelist and not run the application if it does not meet the requirements of the whitelist.
Is your feature request related to a problem? Please describe.
In lieu #279, we should have a way that we can see what resource will be accessed and which components will access those resources. Additionally a whitelist functionality for resources should be available so components can be restricted to which resources they have access even if they are somehow given access accidentally.
Propose a solution
wick run app.wick --dry-run
should load the application but not actually run the application but simply report on the list of all of the resources that are used by the application and which components access them.wick run app.wick --enforce whitelist.wick
should attempt to run the application but compare all of the resources to the resource whitelist and not run the application if it does not meet the requirements of the whitelist.Example of whitelist.wick:
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered: