Add new ModuleConfig fields documentation

cmd/modulectl/create/long.txt

@@ -24,11 +24,22 @@ The module config file is a YAML file used to configure the following attributes
 - security:         a string, optional, name of the security scanners config file
 - labels:           a map with string keys and values, optional, additional labels for the generated ModuleTemplate CR
 - annotations:      a map with string keys and values, optional, additional annotations for the generated ModuleTemplate CR
+- manager: # an object, optional, module resource that indicates the installation readiness of the module
+    name: a string, required, the name of the module resource
+    namespace: a string, optional, the namespace of the module resource
+    group: a string, required, the API group of the module resource
+    version: a string, required, the API version of the module resource
+    kind: a string, required, the API kind of the module resource
+- associatedResources: a list of Group-Version-Kind(GVK), optional, resources that should be cleaned up with the module deletion
+- resources: # a map wih string keys and values, optional, additional resources of the module that may be fetched
+    - name: a string, required, the name of the resource
+      link: a URL, required, the link to the resource
 ```
 
 The **manifest** file contains all the module's resources in a single, multi-document YAML file. These resources will be created in the Kyma cluster when the module is activated.
 The **defaultCR** file contains a default custom resource for the module that is installed along with the module. It is additionally schema-validated against the Custom Resource Definition.
 The CRD used for the validation must exist in the set of the module's resources.
+The **resources** are copied to the ModuleTemplate spec.resources. If it does not have an entry named 'raw-manifest', then the ModuleTemplate spec.resources will populate this entry from the **manifest** field specified in the moduleconfig.
 
 ### Modules as OCI artifacts
 Modules are built and distributed as OCI artifacts. 

docs/gen-docs/modulectl_create.md

@@ -32,11 +32,22 @@ The module config file is a YAML file used to configure the following attributes
 - security:         a string, optional, name of the security scanners config file
 - labels:           a map with string keys and values, optional, additional labels for the generated ModuleTemplate CR
 - annotations:      a map with string keys and values, optional, additional annotations for the generated ModuleTemplate CR
+- manager: # an object, optional, module resource that indicates the installation readiness of the module
+    name: a string, required, the name of the module resource
+    namespace: a string, optional, the namespace of the module resource
+    group: a string, required, the API group of the module resource
+    version: a string, required, the API version of the module resource
+    kind: a string, required, the API kind of the module resource
+- associatedResources: a list of Group-Version-Kind(GVK), optional, resources that should be cleaned up with the module deletion
+- resources: # a map wih string keys and values, optional, additional resources of the module that may be fetched
+    - name: a string, required, the name of the resource
+      link: a URL, required, the link to the resource
 ```
 
 The **manifest** file contains all the module's resources in a single, multi-document YAML file. These resources will be created in the Kyma cluster when the module is activated.
 The **defaultCR** file contains a default custom resource for the module that is installed along with the module. It is additionally schema-validated against the Custom Resource Definition.
 The CRD used for the validation must exist in the set of the module's resources.
+The **resources** are copied to the ModuleTemplate spec.resources. If it does not have an entry named 'raw-manifest', then the ModuleTemplate spec.resources will populate this entry from the **manifest** field specified in the moduleconfig.
 
 ### Modules as OCI artifacts
 Modules are built and distributed as OCI artifacts.