https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/index.html Recent content in 3.7 Git on JP1 Cloud Service/Operations Integration User's Guide Hugo -- gohugo.io en https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/gitreg_gui/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/gitreg_gui/index.html Perform the following operations by accessing GitLab from the Git application. (1) Create the registration destination. Before registering a YAML file, create a registration destination repository in any group. For details on creating a repository, see “Repository management”. Also, before executing the API, it is necessary to perform API authentication and obtain an Ops I token. For details, see “API reference overview > Prerequisite knowledge > Obtaining Ops I tokens” in the “JP1 Cloud Service/Operations Integration API Reference”. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/gitreg_cui/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/gitreg_cui/index.html Perform the following operations in an environment where Git is installed. If the environment requires proxy settings, configure the proxy in advance. Open Git from the working folder in the local environment. (1) Create a clone of the GitLab repository in the local environment and synchronize the local environment with GitLab. Obtaining the GitLab URL Go to the registration destination repository and click "Code". Click the copy button for " https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/accesstoken/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/accesstoken/index.html A GitLab access token must be obtained before operating Git commands. (1) Open the window for obtaining GitLab access tokens. Select "Edit profile" from the submenu displayed when the avatar icon is clicked. The "User settings" menu will appear. Select "Access tokens". This will open the "Personal access tokens" window. (2) Issue a GitLab access token. Click "Add new token". Set the content of the following table then click “Create token” to issue a GitLab access token. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/yaml_diff/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/yaml_diff/index.html (1) Browse to the repository where the YAML file is registered. Browse to the repository created in “Repository management” where the YAML file is registered. (2) Display the updated file list window. Select “Commits” displayed when “Code” is selected in the left side menu to show a list of updated files. (3) Display the file difference display window and confirm the differences. Select the file for which to confirm the differences to display the differences in the file. https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/yaml_ck/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://itpfdoc.hitachi.co.jp/manuals/JCS/JCSM71029001e/function/git/yaml_ck/index.html You can check the registration status of YAML files in Ops I on the GitOps log tab of the system application. When you access the GitOps log tab, the API "gitops-logs" is executed, and the GitOps log (results of executing the API "gitops-logs") is displayed. For details about the GitOps log tab screen, see “GitOps log tab”. [How to read the GitOps log] From the GitOps log, you can check whether operations on YAML files succeeded or failed, as well as file errors (syntax or dependencies) that caused failures.