Comments (5)
ashitr
commented on June 26, 2024
This would help, allowing to ask further inputs based on previous inputs provided.
from script-server.
yosefy
commented on June 26, 2024
exactly!
actually this is the main goal, i couldn't explain it good, thanks
you know what...
may be we can just add some type of "depends_on (list)" field in
script properties, which will show this parameter only when list of
other
param is chosen
wow this would be so cool
this way we will avoid not needing multiple files to include and can
put them all in the same file?
@bugy what do you think?
thanks
…On Thu, Nov 23, 2023 at 11:59 AM Ashit Rai ***@***.***> wrote:
This would help, allowing to ask further inputs based on previous inputs provided.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
from script-server.
bugy
commented on June 26, 2024
Hi, @yosefy could you describe your use case a little bit more detailed? As for me, "depends on" and "include" have slightly different usages:
- "include" should be used for "reusable" configurations, i.e. when multiple scripts use the same configuration
- "depends on" should be used for dynamic visibility of parameters
I guess the main confusion here, is that script server allows "dynamic include", which is probably has nothing to do with reusability. And actually, in many cases, it causes duplicity, because people have to introduce several "included" files for different parameter values.
I think, my preferred solution here would be to add something like enabled option for each parameter, which will call some script and depending on the script results, might include the parameter.
It should be more flexible than depends on, since it will allow to enable a parameter for certain values and even depend on some other conditions (e.g. time of a day 😅)
What do you think?
from script-server.
yosefy
commented on June 26, 2024
use case:
first (main) conf:
- choose list of ansible playbooks (only playbooks drop down list shown)
- if playbook is "install_prometheus_exporter.yaml" show new list of vars
that playbook "install_prometheus_exporter.yaml" needs and playbook B
needs another list of vars
second (include 1) conf:
lets say we choose playbook A which is "install_prometheus_exporter.yaml"
for example
now we see more vars in ui;
hosts_list (hosts to install on)
exporter_type (node_exporter, mysql_exporter, java_exporter)
now that we choose exporter type (in included config), depending on type
there are different set of. vars
for java_exporter we need java_version
for mysql_exporter we need may ber mysql_version, exporter_version, and
mysql_server
and for node exporter we need nothing
=================
hope it will help to choose the right way to implement
thanks
…On Mon, Nov 27, 2023 at 11:22 AM Iaroslav Shepilov ***@***.***> wrote:
Hi, @yosefy <https://github.com/yosefy> could you describe your use case
a little bit more detailed? As for me, "depends on" and "include" have
slightly different usages:
- "include" should be used for "reusable" configurations, i.e. when
multiple scripts use the same configuration
- "depends on" should be used for dynamic visibility of parameters
I guess the main confusion here, is that script server allows "dynamic
include", which is probably has nothing to do with reusability. And
actually, in many cases, it causes duplicity, because people have to
introduce several "included" files for different parameter values.
I think, my preferred solution here would be to add something like enabled
option for each parameter, which will call some script and depending on the
script results, might include the parameter.
It should be more flexible than depends on, since it will allow to enable
a parameter for certain values and even depend on some other conditions
(e.g. time of a day 😅)
What do you think?
—
Reply to this email directly, view it on GitHub
<#722 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADCXF3KV4ZO7CK6H3Y7TSA3YGRLT5AVCNFSM6AAAAAA7VRKTLGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRXGQ2DMMJSGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
from script-server.
Related Issues (20)
- Initialization failure due to failure to read log files HOT 1
- Server_file type parameter issue. HOT 2
- Login Screen - Image behind --login-header-background dialog possible? HOT 2
- Reverse proxy w/Caddy v2 HOT 5
- [HELP] How do I send "ctrl+c" through terminal input? HOT 4
- Question: Is it possible to have a dropdown width smaller than "width": "1" HOT 1
- no demo scripts in sample folder HOT 2
- Feature Request: Add a "Select All" to the parameter type "multiselect" above 1st entry of list HOT 1
- Webinterface is quite cpu consuming HOT 4
- Autostart Scripts after script-server start? HOT 8
- New folder as group support only real folder not link HOT 1
- Build multiarch Docker image HOT 3
- add option for default in list to take first item whatever it is HOT 4
- Crash: 'NoneType' object has no attribute 'translate' when required parameters fields are missing HOT 1
- included configs allow yaml HOT 7
- show ScriptServer version in UI context or config.json HOT 2
- Feature request: support target="_blank" for links in terminal output HOT 2
- Executing an ansible playbook with user + password requires the parameter "same_arg_param" HOT 2
- regex for allowed_users? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from script-server.