1. User's Guide Home >
  2. 4. Designing and Building Your Operation >
  3. 4.6 Registering YAML files with GitLab

4.6 Registering YAML files with GitLab

YAML files developed through the operational design described above take effect only after they are registered in GitLab.
This chapter describes the procedure for registering developed YAML files in GitLab, following the flow of the development process.


Section structure

4.6.1 Process from YAML file code development to actual operation
4.6.2 Uploading YAML files

JP1 Cloud Service/Operations Integration User's Guide
Operations
Integration
  • Home
  • Introduction
  • Changes
  • Contents
  • 1. Outline
    • 1.1 Ops I outline
    • 1.2 Ops I features
    • 1.3 Outline of usage
    • 1.4 Use precautions and temporary restrictions
      • 1.4.1 Use precautions
      • 1.4.2 Temporary restrictions
  • 2. Implementation & Configuration
    • 2.1 Prerequisite knowledge
      • 2.1.1 User implementing & configuring
      • 2.1.2 Association between users and each function
      • 2.1.3 User management functions
    • 2.2 Preparation
      • 2.2.1 Connecting & logging in to Ops I
      • 2.2.2 Setting one-time code
    • 2.3 Creating users
      • 2.3.1 Creating users for using Ops I
      • 2.3.2 Setting roles for created users
    • 2.4 Configuring organization
    • 2.5 Setting a relay server
      • 2.5.1 RPM package
    • 2.6 Setting a repository
    • 2.7 Setting up external IdP linkage
      • 2.7.1 Setting up OIDC connection
      • 2.7.2 Setting up SAML connection
        • 2.7.2.1 Updating SAML certification
      • 2.7.3 Mapping attributes/groups/roles
      • 2.7.4 Log in/log out
    • 2.8 Private network connection to on-premise environment
  • 3. Functions
    • 3.1 Basic window structure
      • 3.1.1 Account management
    • 3.2 Tasks and Requests
      • 3.2.1 Service catalog
      • 3.2.2 Workflow
      • 3.2.3 Tickets
        • 3.2.3.1 incident tickets
        • 3.2.3.2 request tickets
        • 3.2.3.3 task tickets
        • 3.2.3.4 problem tickets
        • 3.2.3.5 rfc tickets
        • 3.2.3.6 release tickets
        • 3.2.3.7 case tickets
        • 3.2.3.8 unclassified tickets
      • 3.2.4 Schedule
        • 3.2.4.1 Calendar management functions
        • 3.2.4.2 Work item management functions
        • 3.2.4.3 Resource-specific scheduling functions
      • 3.2.5 Resources
    • 3.3 Documents
      • 3.3.1 Container
      • 3.3.2 Distribution
    • 3.4 System
      • 3.4.1 User management
        • 3.4.1.1 Users
        • 3.4.1.2 Groups
        • 3.4.1.3 Roles
      • 3.4.2 Identity provider
        • 3.4.2.1 Common settings
      • 3.4.3 Organization management
      • 3.4.4 Outpost management
      • 3.4.5 Repository management
    • 3.5 IT service management (ITSM)
    • 3.6 Secret management
      • 3.6.1 Register a secret
      • 3.6.2 Change a secret
      • 3.6.3 Register user credential information
    • 3.7 Git
      • 3.7.1 Register YAML files with GitLab (GUI)
      • 3.7.2 Register YAML files with GitLab (CUI)
      • 3.7.3 Obtaining GitLab access tokens
      • 3.7.4 Checking differences in YAML files
      • 3.7.5 Checking registration status of YAML files
    • 3.8 Automation
      • 3.8.1 Registering authentication information
      • 3.8.2 Setting projects
      • 3.8.3 Registering inventory
      • 3.8.4 Registering templates
      • 3.8.5 Checking job execution results
  • 4. Designing and Building Your Operation
    • 4.1 Prerequisite knowledge
      • 4.1.1 Associations between functions & required knowledge
      • 4.1.2 Precautions when defining YAML files
    • 4.2 Organizing tasks
      • 4.2.1 Identifying routine/as-needed tasks
      • 4.2.2 User management
      • 4.2.3 Skills required for operation
      • 4.2.4 Organizing handled documents
    • 4.3 Task design
      • 4.3.1 Designing a data model
      • 4.3.2 Designing a workflow
      • 4.3.3 Designing notifications
        • 4.3.3.1 Example of notification of schedule and work item origin
      • 4.3.4 Storing documents
      • 4.3.5 Users and ACL
      • 4.3.6 Skill management
      • 4.3.7 Automation
      • 4.3.8 Ticket management
        • 4.3.8.1 Ticket notification function
        • 4.3.8.2 SLA management function
        • 4.3.8.3 Ticket approval function
      • 4.3.9 Schedule management
      • 4.3.10 Site management
        • 4.3.10.1 Prerequisite knowledge
        • 4.3.10.2 Ops I Menu
        • 4.3.10.3 Embedding the Ops I window in a site
        • 4.3.10.4 Import/export sites
        • 4.3.10.5 Installing themes
        • 4.3.10.6 Multilingual support for sites
        • 4.3.10.7 Notifications
        • 4.3.10.8 Log out from Ops I
        • 4.3.10.9 Changing Ops I password
    • 4.4 UI design
      • 4.4.1 UI version
      • 4.4.2 Defining window URL (Uipath)
      • 4.4.3 Saving a table display
      • 4.4.4 Displaying hint messages
    • 4.5 Other operational design tips
      • 4.5.1 Library
      • 4.5.2 Application
      • 4.5.3 Customizing the ticket window
        • 4.5.3.1 Ticket fields
        • 4.5.3.2 Ticket statuses
        • 4.5.3.3 Ticket types
      • 4.5.4 Customizing the default YAML files
      • 4.5.5 Checking registration status of YAML files (GUI)
    • 4.6 Registering YAML files with GitLab
      • 4.6.1 Process from YAML file code development to actual operation
      • 4.6.2 Uploading YAML files
    • 4.7 Setting up automatic job execution
    • 4.8 Using a relay server
    • 4.9 Linking with other products
      • 4.9.1 JP1/AJS3
      • 4.9.2 JP1/IM
        • 4.9.2.1 Monitoring deterrence
        • 4.9.2.2 Registering incidents
    • 4.10 Extending the environment for automatic execution
  • 5. Operation
    • 5.1 Checking license usage
    • 5.2 Migrating data from verification environment to actual environment
      • 5.2.1 Approach to data migration
      • 5.2.2 Data migration of files in Git repository
    • 5.3 Actions required when upgrading Ops I version
      • 5.3.1 Preserving the customized ticket function
      • 5.3.2 Updating the AWX execution environment
  • 6. YAML Definition
    • 6.1 Workflow
      • 6.1.1 Provided Ops I components
    • 6.2 UI
      • 6.2.1 UI (UI Version 1.0)
      • 6.2.2 UI (UI Version 1.1)
      • 6.2.3 Uipath
    • 6.3 Datamodel
    • 6.4 Catalog
    • 6.5 Script
      • 6.5.1 Action scripts (UI Version 1.0)
      • 6.5.2 Action scripts (UI Version 1.1)
    • 6.6 Library
    • 6.7 Attachment
    • 6.8 Distribution
    • 6.9 ACL, Statement
    • 6.10 Notification, Notifier
    • 6.11 Application
    • 6.12 Skill, Skillset
    • 6.13 Calendar
  • 7. Troubleshooting
    • 7.1 Message list
    • 7.2 How to deal with errors
      • 7.2.1 How to deal with messages
      • 7.2.2 How to deal with YAML syntax errors
  • 8. OPS I Roles
    • 8.1 Correspondence between roles and support functions in Ops I
    • 8.2 Correspondence between API and Ops I roles
  • 9. Appendix
    • 9.1 OSS version/edition and reference manuals
    • 9.2 Version changes
  •  
  •