Updating the resolutionPath of a service entity causes a constraint violation

[rpevertsminvwsnl]

When changing the resolutionPath of an existing service (unchanged goid, guid and name) and and trying to update by importing a graphman bundle (NEW_OR_UPDATE) graphman gives an error:

    {
      "action": "NEW_OR_UPDATE",
      "status": "ERROR",
      "description": "Error creating or updating SERVICE entity, constraint violation - could not execute statement",
      "source": [
        {
          "name": "serviceType",
          "value": "WEB_API"
        },
        {
          "name": "resolutionPath",
          "value": "/updatedpath"
        }
      ]
    }

How can I update only the resolutionpath of a service without removing it first?

[graju256]

The set-based mutation methods do not support modifying the identity specific properties. In this case, resolutionPath is one of the identity property for services.

There's an alternative. We started supporting partial updates for the selective entity types. Fortunately, services are in the support list. Please find the following mutation methods for modifying the service entities. Otherwise, they do not operate on multiple entities.

updateService(refInput: ServiceRefInput!, input: L7ServicePartialInput!)
updateServiceProperties(refInput: ServiceRefInput!, properties: properties: [EntityPropertyPartialInput!]!)

As an example, to modify the resolution path for a given service

updateService(
  refInput: {
    resolutionPath: "/some-service", 
    serviceType: WEB_API
  }, input: {
    resolutionPath: "/some-service-modified"
  }
) {
  detailedStatus {status description source {name value} target{name value}
}

[graju256]

Unfortunately, there's no OTB support for all kind of mutations. In order to work with graphman client, please consider creating user-defined queries. Ref: https://github.com/Layer7-Community/graphman-client/wiki/Command-(Operation)-Reference#creating-your-own-queries

[ecelen-minvws]

Is there going to be support in the future for this situation? Also noticed that for the policy fragement the name is one of the identity properties and can not be updated. Is there documentation of what the identifiers for each entity are and are not able to be updated?

[graju256]

@ecelen-minvws

Supporting standard mutations is on our roadmap for future schema releases.

Certain identity properties, such as names, will be modifiable. We have already started building the partial update mutations required for this functionality.

We will ensure this is properly documented moving forward.