{"diffoscope-json-version": 1, "source1": "/srv/reproducible-results/rbuild-debian/r-b-build.o8vKtDZx/b1/keystone_27.0.0-1_i386.changes", "source2": "/srv/reproducible-results/rbuild-debian/r-b-build.o8vKtDZx/b2/keystone_27.0.0-1_i386.changes", "unified_diff": null, "details": [{"source1": "Files", "source2": "Files", "unified_diff": "@@ -1,4 +1,4 @@\n \n- d524b36b21808104def8e70a5afc51e2 2254548 doc optional keystone-doc_27.0.0-1_all.deb\n+ a703b293728ee4baee6cbab300cb289c 2254476 doc optional keystone-doc_27.0.0-1_all.deb\n 038d3e5828444eedf71d324fd1895db8 71600 net optional keystone_27.0.0-1_all.deb\n 032f3048c83ad7f634ba7500addd4d8e 727288 python optional python3-keystone_27.0.0-1_all.deb\n"}, {"source1": "keystone-doc_27.0.0-1_all.deb", "source2": "keystone-doc_27.0.0-1_all.deb", "unified_diff": null, "details": [{"source1": "file list", "source2": "file list", "unified_diff": "@@ -1,3 +1,3 @@\n -rw-r--r-- 0 0 0 4 2025-04-02 10:53:09.000000 debian-binary\n -rw-r--r-- 0 0 0 28520 2025-04-02 10:53:09.000000 control.tar.xz\n--rw-r--r-- 0 0 0 2225836 2025-04-02 10:53:09.000000 data.tar.xz\n+-rw-r--r-- 0 0 0 2225764 2025-04-02 10:53:09.000000 data.tar.xz\n"}, {"source1": "control.tar.xz", "source2": "control.tar.xz", "unified_diff": null, "details": [{"source1": "control.tar", "source2": "control.tar", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "unified_diff": null, "details": [{"source1": "./md5sums", "source2": "./md5sums", "comments": ["Files differ"], "unified_diff": null}]}]}]}, {"source1": "data.tar.xz", "source2": "data.tar.xz", "unified_diff": null, "details": [{"source1": "data.tar", "source2": "data.tar", "unified_diff": null, "details": [{"source1": "./usr/share/doc/keystone-doc/html/configuration/config-options.html", "source2": "./usr/share/doc/keystone-doc/html/configuration/config-options.html", "comments": ["Ordering differences only"], "unified_diff": "@@ -292,14 +292,100 @@\n
identity.authenticate.pending
You can reduce the number of notifications keystone emits by explicitly opting out. Keystone will not emit notifications that match the patterns expressed in this list. Values are expected to be in the form of identity.<resource_type>.<operation>. By default, all notifications related to authentication are automatically suppressed. This field can be set multiple times in order to opt-out of multiple notification topics. For example, the following suppresses notifications describing user creation or successful authentication events: notification_opt_out=identity.user.create notification_opt_out=identity.authenticate.success
\n \n \ninteger
\n+64
Size of executor thread pool when executor is threading or eventlet.
\n+Group | \n+Name | \n+
---|---|
DEFAULT | \n+rpc_thread_pool_size | \n+
integer
\n+60
Seconds to wait for a response from a call.
\n+string
\n+rabbit://
The network address and optional user credentials for connecting to the messaging backend, in URL format. The expected format is:
\n+driver://[user:pass@]host:port[,[userN:passN@]hostN:portN]/virtual_host?query
\n+Example: rabbit://rabbitmq:password@127.0.0.1:5672//
\n+For full details on the fields in the URL see the documentation of oslo_messaging.TransportURL at https://docs.openstack.org/oslo.messaging/latest/reference/transport.html
\n+string
\n+keystone
The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option.
\n+boolean
\n+False
Add an endpoint to answer to ping calls. Endpoint is named oslo_rpc_server_ping
\n+boolean
\n<None>
This option can be changed without restarting.
\nThe name of a logging configuration file. This file is appended to any existing logging configuration files. For details about logging configuration files, see the Python logging module documentation. Note that when logging configuration files are used then all logging configuration is set in the configuration file and other logging configuration options are ignored (for example, log-date-format).
\n-Group | \n Name | \n |||||||||
---|---|---|---|---|---|---|---|---|---|---|
DEFAULT | \n@@ -367,16 +453,16 @@\n
Group | \n Name | \n ||||||
---|---|---|---|---|---|---|---|
DEFAULT | \n@@ -394,16 +480,16 @@\n
Group | \n Name | \n |||
---|---|---|---|---|
DEFAULT | \n@@ -788,100 +874,14 @@\n
Group | \n-Name | \n-
---|---|
DEFAULT | \n-rpc_thread_pool_size | \n-
integer
\n-60
Seconds to wait for a response from a call.
\n-string
\n-rabbit://
The network address and optional user credentials for connecting to the messaging backend, in URL format. The expected format is:
\n-driver://[user:pass@]host:port[,[userN:passN@]hostN:portN]/virtual_host?query
\n-Example: rabbit://rabbitmq:password@127.0.0.1:5672//
\n-For full details on the fields in the URL see the documentation of oslo_messaging.TransportURL at https://docs.openstack.org/oslo.messaging/latest/reference/transport.html
\n-string
\n-keystone
The default exchange under which topics are scoped. May be overridden by an exchange name specified in the transport_url option.
\n-boolean
\n-False
Add an endpoint to answer to ping calls. Endpoint is named oslo_rpc_server_ping
\n-