1. The standard TOSCA way to assign an artifact to a node, in its minimal form, would include the following steps:

• Define an artifact type (yet another TOSCA line of typing in addition to node types, capability types, data types, interface types, etc.)
• In the node type, provide an artifact definition, which includes:

•                     A reference to a previously defined artifact type
•                      The URI of a concrete file 

               Once a node type is given an artifact, this artifact automatically becomes relevant for all node templates based on that node type

1. In addition to the “minimal” path described in #2, TOSCA also allows more advanced artifact definition scenarios. For example, one or more artifacts can be associated with a specific node template or with a specific interface operation, etc. Let’s start with something basic (#2) though.

Step 1 - define an artifact type
artifact_types:
my_controller_oriented_blueprint_artifact_type:
description: controller blueprint archithive package
derived_from: tosca.artifact.Root
mime_type: application/java-archive
file_ext: [jar, war]

node_types:
org.openecomp.resource.vfc.2018683Vsrecvfc.abstract.nodes.psx:
description:
derived_from:
properties:
capabilities:
requirements:

Step 2 - add an artifact to a node type: based on an artifact type + URI
artifacts:
controller_blueprint:
type: my_controller_oriented_blueprint_artifact_type
file: <URI>

metadata:
invariantUUID: $invariantUUID

UID: $UID
customizationUUID: $customizationUUID
version: '1.0'
name: $CBA-PACKAGE-NAME
description: Complex node type that is used as nested type in VF
type: Artifact
category: Generic
subcategory: Abstract
properties:
min_vf_module_instances: 1