Question
Fernando Borrego Hernández
ES
Last activity: 31 Jul 2023 4:54 EDT
How to manage config files into PEGA PLATFORM as a internal repository?
Hi all,
We are trying to develop a reusable component in PEGA to integrate some external services. In this way, We need to manage some configuration files to reference them from developed functions. The customer doesn't want to provide a NFS or any other external repository, so we should find an alternative for a K8s environment where DDS doesn't seem like as good a solution as we would expect.
What would be the recommended best practice for managing these files within a PEGA tenant?
Can we use the BBDD as a small storage area? How can we refer to the stored files ?
Thanks in advance.
LTI Mindtree
CA
Let me get it the requirements clearly - You're building APIs as reusable components to read and write information to external system. You want to store config files in your Pega environment to make the integration work.
We need to understand file type to make right design solutions, however, here are some options -
1. You can create a directory location on your window/unix server.
2. Grant right type access to directory for your Pega app unix owner/group-owner
3. Store your config files in the location
4. Refer it in Pega based on your requirements.
Fernando Borrego Hernández
ES
@AKSHAY thanks for your kind answer.
The config-file-content data is just parameters that the external service requires to run.
Those steps you shared are what we need to do, but everything inside PEGA if possible. I mean, we are managing PODs from a K8s environment and it is not an option to create a local path or connect to an nfs space.
The best solution should be to save the files in our PEGA DB and reference them from the application as if it were an NFS emulation.
Can we do something like this?
Thanks in advance