We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now, CalmTask is supported inside variables. Even in Runbook, we need to import CalmTask for runbook dynanic variables. Ex:
from calm.dsl.runbooks import runbook, runbook_json from calm.dsl.runbooks import RunbookTask, RunbookVariable as Variable from calm.dsl.builtins import CalmTask @runbook def DslCommunityRunbook(): ntnx_calm_object = Variable.WithOptions.FromTask( CalmTask.HTTP.get( "https://api.github.com/repos/nutanixdev/calm-community/contents/", content_type="application/json", verify=True, status_mapping={200: True}, response_paths={"ntnx_calm_object": "$[?(@.type == 'dir')].name"}, ), is_mandatory=True, ) RunbookTask.Exec.escript(script="print '0'")
Here both type of Task are used. It is creating confusion. Create a diff interface VariableTask that should be used for task inside variable always.
VariableTask
Also restrict the scope of VariableTask that contain tasks that can be used inside variable i.e. HTTP, escript
The text was updated successfully, but these errors were encountered:
Added changes for making connection param configurable via command (#173
57e67b4
) (cherry picked from commit c9380a3257a7624f0c3e7c358584086bc20de4be)
No branches or pull requests
Right now, CalmTask is supported inside variables.
Even in Runbook, we need to import CalmTask for runbook dynanic variables.
Ex:
Here both type of Task are used. It is creating confusion. Create a diff interface
VariableTask
that should be used for task inside variable always.Also restrict the scope of
VariableTask
that contain tasks that can be used inside variable i.e. HTTP, escriptThe text was updated successfully, but these errors were encountered: