refactor(router_core): move hardcoded value to constant for max invitations (fix #5938)

[ramkumargs]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

How did you test it?

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible

[semanticdiff-com]

Review changes with SemanticDiff.

[ThisIsMani]

Change this attach_printable as well.

Log the const value and also try to log the number of requests as well in this.

[ramkumargs]

Changes are done and committed the code.

[ramkumargs]

@ThisIsMani, Changes are done and committed the code.

[ThisIsMani]

@ramkumargs, were you able to test this?

[ThisIsMani]

@ramkumargs, were you able to test this?

Let me know if you need instructions on this.

[ramkumargs]

@ramkumargs, were you able to test this?

Let me know if you need instructions on this.

@ThisIsMani please give me the steps for testing.
Cargo test -- Is throwing error: Package common_utils v0.1.0 (/root/hyperswitch/crates/common_utils) does not have feature router_env. (Trying to look into it) (RHEL env.)

[ThisIsMani]

Hey @ramkumargs, sorry for the late reply.

Steps for testing:

1. Create a user

   curl --location 'http://localhost:8080/user/signup' \
   --header 'Content-Type: application/json' \
   --header 'api-key: test_admin' \
   --data '{
       "email": "email",
       "password": "password"
   }'
   

2. The above API will give a token in the response.

   curl --location 'http://localhost:8080/user/2fa/terminate?skip_two_factor_auth=true' \
   --header 'Authorization: Bearer {token from signup}'
   

3. The above API will give one more token. With that you can hit invite API.

   curl --location 'http://localhost:8080/user/user/invite_multiple' \
   --header 'Content-Type: application/json' \
   --header 'Authorization: Bearer {token from 2FA API}' \
   --data-raw '[
       {
           "email": "email",
           "name": "name",
           "role_id": "merchant_view_only"
       },
       {
           "email": "email2",
           "name": "name2",
           "role_id": "merchant_view_only"
       }
   ]'
   

   • If the number of elements in the requests are more than what you configured, it should throw error.

Let me know if you face any issues. If you were able to check, please attach a screenshot in the description.

[ramkumargs]

Hey @ramkumargs, sorry for the late reply.

Steps for testing:

1. Create a user

   curl --location 'http://localhost:8080/user/signup' \
   --header 'Content-Type: application/json' \
   --header 'api-key: test_admin' \
   --data '{
       "email": "email",
       "password": "password"
   }'
   

2. The above API will give a token in the response.

   curl --location 'http://localhost:8080/user/2fa/terminate?skip_two_factor_auth=true' \
   --header 'Authorization: Bearer {token from signup}'
   

3. The above API will give one more token. With that you can hit invite API.

   curl --location 'http://localhost:8080/user/user/invite_multiple' \
   --header 'Content-Type: application/json' \
   --header 'Authorization: Bearer {token from 2FA API}' \
   --data-raw '[
       {
           "email": "email",
           "name": "name",
           "role_id": "merchant_view_only"
       },
       {
           "email": "email2",
           "name": "name2",
           "role_id": "merchant_view_only"
       }
   ]'
   

   • If the number of elements in the requests are more than what you configured, it should throw error.

Let me know if you face any issues. If you were able to check, please attach a screenshot in the description.

@ThisIsMani , I will test and update you today

[gorakhnathy7]

Hey @ramkumargs Any update here?

[ramkumargs]

Hi @gorakhnathy7 sorry for late reply. I was struck on my some personal issue.
I have started the testing now.

[ramkumargs]

Hi,
When running below command, hanging at => [hyperswitch-web 5/5] RUN npm install
docker compose up -d (Expecting to run this command before executing curl commands)

Am I proceeding in the right way for testing?

[ThisIsMani]

Hey @ramkumargs, did the hyperswitch-server container start without any issues?

[ramkumargs]

Not started. Failing at hyperswitch-hyperswitch-server-1, after long build time

[ThisIsMani]

Can you use cargo run instead.