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

Add embedded scripting language support for more complex workflows #549

Closed
Ice3man543 opened this issue Feb 18, 2021 · 4 comments
Closed
Assignees
Labels
Type: Enhancement Most issues will probably ask for additions or changes.

Comments

@Ice3man543
Copy link
Member

Is your feature request related to a problem? Please describe.

We need to find a good Embeddable Scripting language to add support for even more complex workflows and greater control over the entire process.

Some potential choices to consider - Starlight / Tengo / Lua / Javascript / something else?

@Mzack9999
Copy link
Member

Extensible python dialect skylark/starlight

@ehsandeep ehsandeep added the Type: Enhancement Most issues will probably ask for additions or changes. label Feb 19, 2021
@Mzack9999 Mzack9999 linked a pull request Mar 22, 2021 that will close this issue
@ehsandeep ehsandeep added enhancement and removed Type: Enhancement Most issues will probably ask for additions or changes. labels May 26, 2021
@forgedhallpass forgedhallpass added Type: Enhancement Most issues will probably ask for additions or changes. and removed enhancement labels Oct 7, 2021
@forgedhallpass forgedhallpass changed the title [feature] Add embedded scripting language support for more complex workflows Add embedded scripting language support for more complex workflows Nov 18, 2021
@forgedhallpass forgedhallpass added the Type: Epic Issue including multiple subtasks label Nov 18, 2021
@forgedhallpass forgedhallpass linked a pull request Nov 18, 2021 that will close this issue
@forgedhallpass forgedhallpass added the Priority: High After critical issues are fixed, these should be dealt with before any further issues. label Nov 18, 2021
@Mzack9999
Copy link
Member

Mzack9999 commented Nov 30, 2021

Issues/features associated and dependent on this refactor
- [ ] https://github.com/projectdiscovery/nebula/issues/4
- [ ] Replace https://github.com/Knetic/govaluate with https://github.com/projectdiscovery/nebula ensuring back-compatibility

  • Add new protocol allowing scripting engine snippets (eg. named Code)

- [ ] Once #1162 is merged, improve/adapt it with features from #914 if necessary (eg. cross-template value hashing, visibility scope for exported values template/workflow/global, etc)

This was unlinked from pull requests Dec 3, 2022
@ehsandeep ehsandeep linked a pull request Dec 3, 2022 that will close this issue
4 tasks
@ehsandeep ehsandeep removed the Type: Epic Issue including multiple subtasks label Dec 3, 2022
@dogancanbakir
Copy link
Member

Expr can be an alternative: https://github.com/antonmedv/expr/

@ehsandeep ehsandeep removed a link to a pull request Jun 9, 2023
4 tasks
@ehsandeep
Copy link
Member

This is now being tracked at #549

@ehsandeep ehsandeep closed this as not planned Won't fix, can't repro, duplicate, stale Jun 9, 2023
@ehsandeep ehsandeep removed the Priority: High After critical issues are fixed, these should be dealt with before any further issues. label Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Most issues will probably ask for additions or changes.
Projects
None yet
Development

No branches or pull requests

5 participants