Re: [tosca] Operation implementations

[adam souzis <adam@souzis.com>]

Yes, an artifact represents a file-like bag of data, and for example, a DevOps deployment process can interact with artifacts in a myriad ways, whether its container images, build process artifacts, artifact registries like JFrog, files destined for a cloud object store like AWS S3, deployment artifactsÂlike Terraform state files, etc. I see its use as representing an implementation as secondary and probably confusing for most users if we overload its meaning to mean any interface to an executable process.

á

On Wed, Sep 8, 2021 at 11:46 AM Tal Liron <tliron@redhat.com> wrote:

On Wed, Sep 8, 2021 at 1:32 PM Chris Lauwers <lauwers@ubicity.com> wrote:

Hi Tal, would you mind clarifying the two roles that artifact types take on? Based on my understanding, the artifact type is only there to inform the orchestrator which code needs to be executed to âcallâ the artifact (or, using Adamâs terminology, which Configurator to use). Do you see another role for artifact types?

I see many roles for artifacts that have nothing to with operations:

1. Virtual machine images attached to nodes

2. Policy definitions for specialized agents

3. Schemas for special data type validation (e.g. YANG)

...