Resources
REST and SOAP-based flows rely on OpenAPI and WSDL specification files, respectively, to create their endpoints.
However, the contents of these files are not attached directly to the flow/processor.
Instead, they are referenced by an ID such as OpenAPIv3:simple-rest-api:latest.
The flow-server, in turn, uses this ID to look up the corresponding file from the "Resource Registry".
Thus, endpoint specifications are treated as separate entities (i.e., resources) that must be deployed alongside the flows that need them.
Supported Data Types
The Resource Registry can hold more than just OpenAPI specs and WSDL documents. The following table highlights the different data types that are supported:
| Type | Description |
|---|---|
Resources |
Specifications for REST and SOAP endpoints, and validation schemas for JSON and XML. |
Secrets |
Sets of key/value pairs used to authenticate against other systems (e.g., databases, external REST APIs, etc.). |
Dynamic Tables |
Small-scale, user-defined data structures for storing common lookup values or cross-referenced IDs. |
| Secrets are persisted in a secure vault and, therefore, cannot be viewed or retrieved after they are deployed to the flow-server. |