Printing service

The printing service is automatically deployed along side the core-service. The Chart needs to define the Packaging Control modules and their alias which is corresponding to the Chart.Name.

If the printing provider and its required parameters are not configured in the helmchart, the service will start but will log errors and report as unhealthy. If the printing provider is not configured, features such as printing internal labels are not available and will return a 503 http status code when called.

Currently supported providers:

"OmsRest" - Bosch Output Management System via REST

Config - YAML format

Custom-Values.yaml Either other extending the config maps or by adding them to the env

Variables:

"NEXEED_PACO_PRINTING_SERVICE_PrintProvider__Type": "OmsRest"
"NEXEED_PACO_PRINTING_SERVICE_PrintProvider__OmsRest__PrintURL": "<PrintURL>?printer={PrinterName}"
"NEXEED_PACO_PRINTING_SERVICE_PrintProvider__OmsRest__AuthenticationHandler__Type": "Oauth"|null
"NEXEED_PACO_PRINTING_SERVICE_PrintProvider__OmsRest__AuthenticationHandler__TokenURL": "<TokenUrl>"
"NEXEED_PACO_PRINTING_SERVICE_PrintProvider__OmsRest__AuthenticationHandler__ClientId": "<ClientId>"
"NEXEED_PACO_PRINTING_SERVICE_PrintProvider__OmsRest__AuthenticationHandler__ClientSecret": "<ClientSecret>"
"NEXEED_PACO_PRINTING_SERVICE_PrintProvider__OmsRest__AuthenticationHandler__Scope": "<SCOPE>"
"NEXEED_PACO_PRINTING_SERVICE_PrintProvider__OmsRest__AuthenticationHandler__GrantType": client_credentials

paco:
  configmaps:
    paco-service-configmap:
      [insert key values from above]

or by adding the env to the deployment

paco:
   deployments:
      printing-service:
            env:
               [insert key values from above]

Config - JSON format

"PrintProvider": {
  "Type": "OmsRest",
  "OmsRest": {
    "PrintURL": "<PrintURL>?printer={PrinterName}",
    "Proxy": {
        "Type": "system"
      },
    "AuthenticationHandler": {
      "Type": "Oauth",
      "TokenURL": "<TokenUrl>",
      "ClientId": "<ClientId>",
      "ClientSecret": "<ClientSecret>",
      "GrantType": "client_credentials",
      "Scope": "<SCOPE>",
      "Proxy": {
        "Type": "system"
      }
    }
  }
}

Authentication configuration

Type: Sets what kind of auth is used.

Possible values:

null, "Oauth"

Proxy configuration

Per connection a Proxy is configurable

Proxy can be

undefined|null,

No Proxy will be used.

"Proxy": {
    "Type": "system"
    },

The Proxy defined by HTTPS_PROXY or HTTP_PROXY Environment variables will be used as well NO_PROXY values. Priority is HTTPS and then HTTP.

The Env vars of the host system will not automatically passed to the container, see below

How to configure the proxy in the inventories:

Global configuration:

global:
  proxy:
    enabled: <true|false>
    httpProxy: <proxyUrl>    # e.g. http://rb-proxy-sl.bosch.com:8080
    httpsProxy: <proxyUrl>   # e.g. http://rb-proxy-sl.bosch.com:8080
    noProxy: <noProxyConfig> # e.g. localhost,127.0.0.1,svc,local,bosch.com

Example to pass host Proxy to the deployment

global:
  proxy:
    enabled: true
    httpProxy: {{ .Env.HTTP_PROXY | quote }}
    httpsProxy: {{ .Env.HTTPS_PROXY | quote }}
    noProxy: {{ .Env.NO_PROXY | quote }}

"Proxy": {
    "Type": "manual",
    "URL": "http://localhost:3128",
    "NoProxyFor": "*.bosch.com,localhost"
    }

The defined Proxy will be used, Authentication at the Proxy is currently not supported.