Each Cloud Retrofit process uses a different set of configuration files to provide
PolicyCenter with information about how to generate LOB-specific endpoints for a given
non-APD native product:
Cloud Retrofit Process |
Files used by the process |
Cloud Retrofit without APD App |
- <lob_prefix>_codegen_config_ext-1.0.yaml
- template_gen_config.xml
|
Cloud Retrofit with APD App |
- <lob_prefix>_codegen_config_ext-1.0.yaml
- template_gen_config.xml
- template_gen_config.all.yaml
- template_gen_config.<lob_prefix>.yaml
|
- <lob_prefix>_codegen_config_ext-1.0.yaml
- Defines aspects of how the REST APIs are generated. For example, you can
define overrides for certain behaviors such as auto-numbering and available
endpoints for a particular type. These files can be used anytime REST API
endpoints are generated, including APD conversion, Cloud Retrofit, and APD
native.
- template_gen_config.xml
- Defines the APD model structure needed to generate LOB-specific endpoints
for the Cloud Retrofit without APD App process. For the Cloud
Retrofit with APD App process, this file needs to be edited to
remove LOB-specific information for LOBs that you create in the APD app.
- template_gen_config.all.yaml
- Defines aspects of how the REST APIs are generated for Cloud Retrofit
with the APD App and APD conversion. This file is available in the
base configuration and it applies to all LOBs. If required, you can modify
the file to change default values and define configuration details that
can't be automatically inferred from the data model when generating the REST
APIs.
- template_gen_config.<lob_prefix>.yaml
- Template gen config YAML files are used for Cloud Retrofit with the APD
App and APD conversion. This LOB-specific file allows you to change
default values and define configuration details that can't be automatically
inferred from the data model when generating the REST APIs.