4.5.4 Customizing the default YAML files

The “default YAML files” that define the Ops I UI and applications are registered in Ops I in advance. Some of the default YAML files can be edited to customize ticket management and other operation windows.

This section describes where those default YAML files that can be edited are located.
Ops I provides the following groups and repositories accessible to users and the default YAML files are registered in the “apps” repository for “Ops I System Engineers”.
The directory structure of “apps” differs depending on the type of the YAML file.

(Table) Ops I groups and repositories

Group Repository Description
Ops I System Engineers apps
  • Of the existing YAML files that define the Ops I UI and applications, YAML files that users can edit are registered here.
  • By editing those files, some of the Ops I operation windows can be customized.
global global
  • This repository can be used as a repository to store shared containers using the Library function or as a repository to distribute attached files.
  • Because all users belong to this group, the "global" repository is accessible to all users.
Creating users Creating users
  • This repository can be used as a repository to store shared containers using the Library function or as a repository to distribute attached files.
  • This repository can be used as a registration destination for new YAML files for service catalogs, workflows, UI, Script, etc.

Users must belong to an appropriate group to access this repository. Appropriate Git roles also need to be set up according to use cases. For details on Git roles, see “(Table) Related resources area tabs when adding a group”.

For an examples of changing an operation window by customizing the default YAML file, see “Customizing the ticket window”.

NotesNotes

  • The initial YAML file may be updated when the Ops I version is upgraded.
  • When customizing the initial YAML file, the customer needs to maintain the code.
  • If the customized parts of the initial YAML file conflict with changes made during the Ops I upgrade, the customer needs to resolve the conflict. When upgrading Ops I, check that the customized parts are working properly.