Gerhard Muth

I've written a jvm-based tool [inspectprinter.sh](https://github.com/gmuth/ipp-samples/blob/main/inspectprinter.sh) that runs a few [ipp operations](https://github.com/gmuth/ipp-samples/blob/main/src/main/kotlin/ipp/InspectPrinter.kt) and saves the [ipp responses](https://github.com/gmuth/ipp-samples/tree/main/printers). Anyone can fork the github repository [ipp-samples](https://github.com/gmuth/ipp-samples), run the tool, commit and push...

I have [patched kube-deployment.yml](https://github.com/gmuth/k8s-wordsmith-demo/commit/08cece6b543cac51fcfe2146e3fa7e5087c5d989) in order to have kubernetes use the local arm64 images instead of pulling the amd64 images.

Hint: [IppCollection](https://github.com/gmuth/ipp-client-kotlin/blob/master/src/main/kotlin/de/gmuth/ipp/core/IppCollection.kt) implemented in [ipp-client-kotlin](https://github.com/gmuth/ipp-client-kotlin) does not have this limitation and can take/read/write any attribute type as member (also collections).

This demonstrates how to discover ipp printers using bonjour/zeroconf: https://github.com/gmuth/ipp-samples/blob/main/src/main/kotlin/mdns/DiscoverIppPrinters.kt

On Mac M1 running macOS 12.5.1 it looks good now: ``` % az version { "azure-cli": "2.39.0", "azure-cli-core": "2.39.0", "azure-cli-telemetry": "1.0.6", "extensions": { "account": "0.2.3", "spring": "1.1.5", "ssh": "1.1.2" }...

The drop down indeed allows to visualize all graphQL operations: Queries, Mutations and Subscriptions. Maybe a title like "Operations:" next to the select-from-list component would help.

Until jipp supports notifications you could use https://github.com/gmuth/ipp-client-kotlin which already supports notifications and [subscriptions](https://github.com/gmuth/ipp-client-kotlin/blob/master/src/main/kotlin/de/gmuth/ipp/client/IppSubscription.kt) compatible with IPP infra.

Two issues need to be fixed here: 1. **azure-function infrastructure needs to acknowledge/accept any mime types** and not just e.g. application/octet-stream as binary content. suggestion: consider binary the default and...

Even the IPP reference implementation CUPS sometimes responds with duplicate attributes. So resilience for this issue is highly recommended. Adding the attribute again sounds okay to me.

Alternatively you could use this [CupsClient](https://github.com/gmuth/ipp-client-kotlin/blob/master/src/main/kotlin/de/gmuth/ipp/client/CupsClient.kt) which supports already some additional CUPS operations (e.g. job subscriptions and printer setup)