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
We would like to deploy the smart contracts several times (for example on dev, test, preprod and prod platforms).
This means having the same ABI, but with different addresses.
This is configured by the src/config.ts file, which is generated from the ABI and addresses in alastria-identity repo content when alastria-identity-lib is installed.
As this file is generated upon installation, there is currently no 'easy' way to configure the smart contracts addresses to be used.
Currently, the only way to achieve this is to have one branch of the alastria-identity repo per smart contracts deployment, containing the addresses specific to this deployment and then used by the alastria-identity-lib to generate the config file.
Business need
We would like to be able to set smart contracts addresses dynamically in the Alastria Identity Library.
Possible solutions
A possible way that we are thinking about is to override the smart contracts addresses using environments variables.
This could be made optional (if the environments variables are not set, the value from the alastria-identity is still used), so it would be a non-breaking change with no impact on existing users.
We will try to provide a pull request in the next days.
The text was updated successfully, but these errors were encountered:
Description
We would like to deploy the smart contracts several times (for example on dev, test, preprod and prod platforms).
This means having the same ABI, but with different addresses.
This is configured by the
src/config.ts
file, which is generated from the ABI and addresses inalastria-identity
repo content whenalastria-identity-lib
is installed.As this file is generated upon installation, there is currently no 'easy' way to configure the smart contracts addresses to be used.
Currently, the only way to achieve this is to have one branch of the
alastria-identity
repo per smart contracts deployment, containing the addresses specific to this deployment and then used by thealastria-identity-lib
to generate the config file.Business need
We would like to be able to set smart contracts addresses dynamically in the Alastria Identity Library.
Possible solutions
A possible way that we are thinking about is to override the smart contracts addresses using environments variables.
This could be made optional (if the environments variables are not set, the value from the
alastria-identity
is still used), so it would be a non-breaking change with no impact on existing users.We will try to provide a pull request in the next days.
The text was updated successfully, but these errors were encountered: