Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move relayer inventory config to external json file #45

Merged

Conversation

matjazv
Copy link

@matjazv matjazv commented Aug 19, 2024

What was the problem?

This PR resolves LISK-885.

How was it solved?

  • Instead of using RELAYER_INVENTORY_CONFIG variable which has json string, RELAYER_EXTERNAL_INVENTORY_CONFIG is used containing file path to json file with a relayer inventory config.

How was it tested?

Run yarn relay --wallet void --address <ADDRESS>, after setting RELAYER_EXTERNAL_INVENTORY_CONFIG variable in .env file.

@matjazv matjazv self-assigned this Aug 19, 2024
@matjazv
Copy link
Author

matjazv commented Aug 19, 2024

Where would we like to store json file for relayer inventory config?
Currently it's inside root folder.
Do we want to create a new folder config for example and put it there?

@sameersubudhi
Copy link
Member

sameersubudhi commented Aug 19, 2024

Where would we like to store json file for relayer inventory config?

Maybe, let's add it to config/mainnet/relayerExternalInventory.json?

Copy link
Member

@sameersubudhi sameersubudhi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works as expected 👍

Ran yarn relay --wallet void --address <ADDRESS> with SEND_RELAYS=false in .env file.
To get it running on Lisk Sepolia, I'd to use the contract addresses instead of the token symbols under tokenConfig in the relayer inventory config.

@sameersubudhi sameersubudhi merged commit c7fdddd into master Aug 20, 2024
1 check passed
@sameersubudhi sameersubudhi deleted the LISK-885-move-across-inventory-config-to-external-file branch August 20, 2024 06:32
sameersubudhi pushed a commit that referenced this pull request Sep 6, 2024
### What was the problem?

This PR resolves LISK-885.

### How was it solved?

- [x] Instead of using `RELAYER_INVENTORY_CONFIG` variable which has
`json` string, `RELAYER_EXTERNAL_INVENTORY_CONFIG` is used containing
file path to `json` file with a relayer inventory config.

### How was it tested?

Run `yarn relay --wallet void --address <ADDRESS>`, after setting
`RELAYER_EXTERNAL_INVENTORY_CONFIG` variable in `.env` file.
sameersubudhi pushed a commit that referenced this pull request Sep 10, 2024
### What was the problem?

This PR resolves LISK-885.

### How was it solved?

- [x] Instead of using `RELAYER_INVENTORY_CONFIG` variable which has
`json` string, `RELAYER_EXTERNAL_INVENTORY_CONFIG` is used containing
file path to `json` file with a relayer inventory config.

### How was it tested?

Run `yarn relay --wallet void --address <ADDRESS>`, after setting
`RELAYER_EXTERNAL_INVENTORY_CONFIG` variable in `.env` file.
sameersubudhi pushed a commit that referenced this pull request Sep 10, 2024
### What was the problem?

This PR resolves LISK-885.

### How was it solved?

- [x] Instead of using `RELAYER_INVENTORY_CONFIG` variable which has
`json` string, `RELAYER_EXTERNAL_INVENTORY_CONFIG` is used containing
file path to `json` file with a relayer inventory config.

### How was it tested?

Run `yarn relay --wallet void --address <ADDRESS>`, after setting
`RELAYER_EXTERNAL_INVENTORY_CONFIG` variable in `.env` file.
sameersubudhi pushed a commit that referenced this pull request Sep 10, 2024
### What was the problem?

This PR resolves LISK-885.

### How was it solved?

- [x] Instead of using `RELAYER_INVENTORY_CONFIG` variable which has
`json` string, `RELAYER_EXTERNAL_INVENTORY_CONFIG` is used containing
file path to `json` file with a relayer inventory config.

### How was it tested?

Run `yarn relay --wallet void --address <ADDRESS>`, after setting
`RELAYER_EXTERNAL_INVENTORY_CONFIG` variable in `.env` file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants