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
The TOSCA community could benefit from the definition of a collection of common implementation artifact types that can be handled the same way by many orchestrators. I’m thinking specifically about shell scripts, python scripts, Ansible playbooks, and Terraform scripts. In addition to the type definitions themselves, we would also define how input values are expected to be passed to those implementation artifacts, how outputs are expected to be returned, how to specify whether an artifact is expected to be “processed” on the orchestrator machine or on a remote machine, how credentials are managed, etc.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The TOSCA community could benefit from the definition of a collection of common implementation artifact types that can be handled the same way by many orchestrators. I’m thinking specifically about shell scripts, python scripts, Ansible playbooks, and Terraform scripts. In addition to the type definitions themselves, we would also define how input values are expected to be passed to those implementation artifacts, how outputs are expected to be returned, how to specify whether an artifact is expected to be “processed” on the orchestrator machine or on a remote machine, how credentials are managed, etc.
Beta Was this translation helpful? Give feedback.
All reactions