GraphQL: node set dependencies, full node graph

[MarkusHorstmann]

This PR uses a NodeSet model (from the CESMII Profile Designer) and the widely used GraphQL "Hot Chocolate" library to expose a fully resolved object graph of all nodes in the nodesets. It is deployed in the CESMII Stage Cloud Library for easier evaluation.

Open issues:

• Compatibility with current graphql schema

Done.

• Use the CESMII NuGets or clone the source (https://github.com/cesmii/CESMII-NodeSet-Utilities)?

Decided to use the NuGet packages.

• Should invalid models continue to be allowed? (Currently there are 5 such models)

Models are allowed but marked as having validation errors.

Try:

# Interfaces in all nodesets
query MyQuery {
  interfaces {
    nodes {
      browseName
    }
  }
}

# DeviceType and its first 3 super  types
query MyQuery {
  objectTypes(nodeId: "nsu=http://opcfoundation.org/UA/DI/;i=1002") {
    nodes {
      browseName nodeId
      properties {
        browseName nodeId
      }
      superType {
        browseName nodeId
        superType {
          browseName nodeId
          superType {
            browseName nodeId
          }
        }
      }
    }
  }
}

# Object types that contain "Vendor" or "Server" in their browseName
query MyQuery {
  objectTypes(where: {or: [{browseName: {contains: "Vendor"}}, {browseName: {contains: "Server"}}]}) {
    nodes {
      browseName
    }
  }
}

# Node sets, their required models, and the actual models/versions found in the cloud library
query MyQuery {
  nodeSets {
    nodes {
      modelUri
      publicationDate
      identifier
      requiredModels {
        modelUri
        publicationDate
        version
        model {
          modelUri
          publicationDate
          version
          identifier
        }
      }
    }
  }
}

[BoBiene]

as requested in #106 we need API stability.
There is a released product using the API (https://www.opc-router.com/opc-router-4-27-update/)

[malessainray]

as requested in #106 we need API stability. There is a released product using the API (https://www.opc-router.com/opc-router-4-27-update/)

I strongly suggest converting this pullrequest to a draft as long as API stability is not ensured. Taking care of #48 first could ease the reviewing burden regarding API compatibility.

[BoBiene]

Compatibility with current graphql schema

[malessainray]

@MarkusHorstmann is the https://cloudlib-back-stage.azurewebsites.net/graphiql running the same version as in this pr?

Yes, essentially. Identical in graphql and data index: cesmii/CESMII-CloudLibrary@opcContrib/mhdev...cesmii:cesmii/develop

Sadly I cannot login or register there for the live of me. Please get in touch with me so that we can perform tests against the staging deployment.

[MarkusHorstmann]

Sadly I cannot login or register there for the live of me. Please get in touch with me so that we can perform tests against the staging deployment.

Your logins should now work. Please try again. There was an issue with the mailer.

[malessainray]

These changes break our client side implementation in shipping product of dependency resolution for nodesets. With the instance hosted at https://uacloudlibrary.opcfoundation.org/ it works fine. I will follow up with more details on what specifically changed.

[malessainray]

The from the method Opc.Ua.CloudLib.Client.UACloudLibClient.GetNamespacesAsync() returned tuple values for the identifiers all have a leading space. This in turn results in failing to download the nodeset using the exact identifier as in no place any string trimming is performed. The stable instance does not return those leading spaces.

[MarkusHorstmann]

The from the method Opc.Ua.CloudLib.Client.UACloudLibClient.GetNamespacesAsync() returned tuple values for the identifiers all have a leading space. This in turn results in failing to download the nodeset using the exact identifier as in no place any string trimming is performed. The stable instance does not return those leading spaces.

Fixed and added a test.

[malessainray]

Fixed and added a test.

@MarkusHorstmann when will the latest changes in this pullrequest be deployed to the staging instance for integration testing?

[MarkusHorstmann]

@MarkusHorstmann when will the latest changes in this pullrequest be deployed to the staging instance for integration testing?

@malessainray It is now deployed at https://cloudlib-back-stage.azurewebsites.net/.

The PR now retains full compability. Please re-review.

[malessainray]

I could no longer spot incompatibilities with our released product.