6.8 Distribution
Distribution definitions and definition examples are shown below. For details on Distribution, see “Storing documents”.
(Table) Distribution definitions
| Label | Default value | Required | Description | ||
|---|---|---|---|---|---|
| apiVersion: | 1.0 | Yes | API version | ||
| kind: | Yes | Specify "distribution" for Distribution. | |||
| type: | No | Only "resource" can be specified for Distribution. | |||
| name: | Yes | Internal name of the Distribution definition. Specify the directory name for this YAML file. | |||
| label: | No | YAML file display name | |||
| description: | No | Detailed description of this YAML file | |||
| includes: | No | List the related YAML files for use in this YAML file. | |||
| - kind: | Yes | Type of YAML file to be loaded | |||
| name: | Yes | Internal name of YAML file to be loaded | |||
| rules: | Yes | Distribution rules | |||
| - name: | Yes | Rule name | |||
| label: | Yes | Rule display name | |||
| group: | Yes | Configure settings for the group to be distributed to. | |||
| type: | Yes | Specify rules to determine the group to which the document will be distributed. The types that can be specified are as follows.
|
|||
| name: | No | Specify the group name to be stored when "fixed" is specified for the type. | |||
| repository: | Yes | Configure settings for the repository to be distributed to. | |||
| type: | Yes | Specify rules to determine the repository in which the document will be stored. The types that can be specified are as follows.
|
|||
| name: | No | Specify the repository name to be stored when "fixed" is specified for the type. | |||
| directory: | Yes | Configure settings for the directory to be distributed to. | |||
| type: | No | The types that can be specified are as follows.
|
|||
| path: | Yes | Specify the path of the directory where the documents will be stored. Characters and character strings that cannot be used in Windows/Linux file and folder names cannot be specified. |
|||
| branch: | Yes | Specify the branch where the documents will be stored. Use the main branch as the branch. | |||
<Definition example>
apiVersion: 1.0
kind: distribution
type: resource
name: VM Creation and Deletion
label: VM Creation and Deletion
description: Classify attachments when generating VMs into groups for each customer.
rules:
- name: VM Creation and Deletion
label: VM Creation and Deletion
group:
type: customer
repository:
type: fixed
name: Evidence
directory:
type: fixed
path: /vm
branch: main