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

Make subsetting the standard environment simple #290

Open
TristonianJones opened this issue Dec 18, 2019 · 2 comments
Open

Make subsetting the standard environment simple #290

TristonianJones opened this issue Dec 18, 2019 · 2 comments
Labels

Comments

@TristonianJones
Copy link
Collaborator

@TristonianJones TristonianJones commented Dec 18, 2019

Feature request checklist

  • There are no issues that match the desired change
  • The change is large enough it can't be addressed with a simple Pull Request
  • If this is a bug, please file a Bug Report.

Change
Currently it is easy to extend a standard environment, but painful to subset it. Effectively, the user must copy and paste code from the supported library which is less than ideal.

Make it possible to specify in terms of types and operators which functionality they would like to support and ensure that only this subset is exposed at check-time and evaluation time.

@TristonianJones
Copy link
Collaborator Author

@TristonianJones TristonianJones commented Apr 30, 2020

Custom environments are difficult to construct since its non-trivial to subset the standard CEL environment. In addressing this feature request an example, as requested in #344, should be added to the cel_test.go file.

@TristonianJones
Copy link
Collaborator Author

@TristonianJones TristonianJones commented Jun 19, 2020

Note, google/cel-policy-templates-go#14 permits the specification of a CEL environment via YAML and would be a good reference for supporting environment subsetting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.