We abstract environment specific configuration (e.g., dev/qa/prod) in rules that have access to all sources by retrieving key/value data from a CSV source.
What are options for before/after scripts for IQService where there is no access to other sources and environment specific must be implemented in the script?
I want to avoid maintaining a discrete source control repository for each environment.
Hi @josephcasale
A JSON file can be created and uploaded to the IQ server. In the script, this JSON file should be referred to for fetching key values. The same JSON file can be used across different environments, with only the key values differing per environment. This approach ensures that hardcoding in the script is avoided.
Incase for cloud rules you can hardcode those values in source directly under connector attributes and rule can fetch those values directly from source json.
Hi @gourab ,
I gather you are referring to Configuration Hub? I am interesting in reading up on this.
Would that JSON file that gets sent to the IQ Server be managed by the instance, or do I need to place it on the IQ Server myself?
Thank you for the guidance.
Hi @josephcasale
You can create the json file manually and manually put it into the server. The file will only hold environment specific values.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.