The Catalog
A deployment exposes the features it knows about and the products that bundle them as one catalog. The catalog is read-only. It lists what the deployment supports, not what a given license grants. A VDX deployment also includes VDX's features in the same catalog.
What the catalog answers
For features, the catalog answers two questions:
- the declared feature for a given key, with its value type, description, and the products that may include it, or nothing if the key is not in the catalog;
- every feature the deployment knows about, for inventory and admin surfaces.
A key the catalog does not list is unknown. The resolver treats an unknown required feature as a denial rather than an implicit grant.
For products, the catalog answers:
- the product for a given product id, with its display name and editions;
- the feature keys a given edition of a product grants, used when a purchased
(product, edition)is expanded into the signed feature set at license-issue time.
Reading it through the API
An operator can read the feature catalog through the Platform Admin API. Each entry carries the feature key, its value kind, a description, and the products that may include it. This is the surface the admin console uses to render its feature and entitlement views. See the Platform Admin API reference.
Where the catalog fits
- Features and Products and SKUs are the data the catalog exposes.
- Entitlement Resolution consults the catalog when a command declares a feature key, denying any key the catalog does not list.