48a94e00a7
The ServiceTypes class is the main entry point for python programmers. It should allow them to answer the questions they have about the data without necessarily walking the structure. It can also return the raw structure if people want to get at it. We need to know the project codename for services for doing API doc publication validation and also for being able to send legacy microversion headers. The information is in the data, use it. In order to construct and send microversion headers for projects with aliases, we need to know ALL of the aliases plus the official name, because we don't know which one of the values will be the correct name the service is looking for for a given version. The microversion spec, however, requires that consumers be able to handle a header that contains a list of services and to ignore the ones it isn't looking for. By providing a a list of all the possible values we make it easy to construct a header for a service given a service_type that should work for all known identifiers of the service and that is future compatible with the service-type and microversion specifyier aligning. Co-Authored-By: Doug Hellmann <doug@doughellmann.com> Change-Id: I57641c9e3c27688b6d7709b1bb07292740d26659 |
||
|---|---|---|
| .. | ||
| contributor | ||
| install | ||
| library | ||
| reference | ||
| conf.py | ||
| index.rst | ||
| readme.rst | ||