You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ensure that the CREDEBL service is in a running state before proceeding.
Steps to Reproduce Current Behavior
Start the api-gateway.
Start the Issuance service.
Current Behavior
Upon initiating the services, it is observed that Redis is a prerequisite for both the api-gateway and the Issuance service. Without Redis, the services fail to operate as expected.
Expected Behavior
Redis should be utilized to persist issuance data, which is particularly critical for the bulk-issuance feature. However, there should be a mechanism to disable the Redis dependency for users who do not require the bulk-issuance functionality. This would allow the services to run without Redis if bulk-issuance is not needed.
Detailed Description
Currently, the system architecture mandates Redis for both the api-gateway and the Issuance service, even for users who do not utilize the bulk-issuance feature. This dependency should be optional, enhancing flexibility and reducing unnecessary overhead for users with different requirements. The expected modification should:
Ensure Redis is only required when the bulk-issuance feature is enabled.
Allow the services to function without Redis when bulk-issuance is disabled.
Additional Information
The api-gateway and Issuance service should have configuration options to enable or disable Redis usage.
Appropriate documentation and guidelines should be provided for users to configure these options based on their specific needs.
This enhancement will improve the usability and adaptability of the system, catering to a broader range of user scenarios.
The text was updated successfully, but these errors were encountered:
Prerequisites
Ensure that the CREDEBL service is in a running state before proceeding.
Steps to Reproduce Current Behavior
Start the api-gateway.
Start the Issuance service.
Current Behavior
Upon initiating the services, it is observed that Redis is a prerequisite for both the api-gateway and the Issuance service. Without Redis, the services fail to operate as expected.
Expected Behavior
Redis should be utilized to persist issuance data, which is particularly critical for the bulk-issuance feature. However, there should be a mechanism to disable the Redis dependency for users who do not require the bulk-issuance functionality. This would allow the services to run without Redis if bulk-issuance is not needed.
Detailed Description
Currently, the system architecture mandates Redis for both the api-gateway and the Issuance service, even for users who do not utilize the bulk-issuance feature. This dependency should be optional, enhancing flexibility and reducing unnecessary overhead for users with different requirements. The expected modification should:
Ensure Redis is only required when the bulk-issuance feature is enabled.
Allow the services to function without Redis when bulk-issuance is disabled.
Additional Information
The api-gateway and Issuance service should have configuration options to enable or disable Redis usage.
Appropriate documentation and guidelines should be provided for users to configure these options based on their specific needs.
This enhancement will improve the usability and adaptability of the system, catering to a broader range of user scenarios.
The text was updated successfully, but these errors were encountered: