Creating a configuration file
The integration between the platform Aranda Service Management Suite (ASMS) and DevOps, is done by setting up a file in JSON format. It is based on the following conceptual model:
Information to take into account:
- Instructions for getting the ASMS id’s used in the configuration file, using the ASMS API with the postman tool Instructions here
A continuación se presenta la definición del modelo conceptual:
| Properties | Description | |
|---|---|---|
| project: | Relate the ASMS project, category, and service to the project in DevOps | See more |
| Case: | Allows you to relate the fields of the Aranda Case to the fields of the WorkItem in DevOps | See more |
| itemType: | Relationship of ASMS Case Types to the “Work Item Type” in DevOps | See more |
| model: | Represents the relationship of the state and additional fields in ASMS cases to the state and fields of the “Work Item Type” in DevOps | See more |
| typeRegister: | Relate the type of record in ASMS cases to the type of record in DevOps | See more |
| Responsible: | Match the ASMS case manager to the DevOps manager | See more |
| responsibleGroup: | Relate the group responsible for ASMS cases to the group responsible in DevOps | See more |
| Applicant: | Match the requester of ASMS cases to the requester in DevOps | See more |
| Company: | Relates ASMS Cases Company to Company in DevOps | See more |
| Client: | Relate the customer of ASMS cases to the customer in DevOps | See more |
| Ci: | Relate the CI of ASMS cases to the CI in DevOps | See more |
| Impact: | Represents the relationship of criticality ASMS cases to DevOps cases | See more |
| Urgency: | Represents the relationship of criticality ASMS cases to DevOps cases | See more |
Below you can download the json structure that will be used throughout the documentation.