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
The migration api can be run on the deployment environment only after the 100% deployment of the specific version of hyperswitch, because there are probabilities of merchant account being created even during the deployments. Once deployment beings the apple pay details must be read from the metadata only until the migrations are done. Hence we need a fallback here which tries to read the apple pay data from the newly added column whenever need and if it fails we just log the error and try to read the apple pay data from the metadata.
Once the migration is done we can check for the error log lines during the read form newly added column, if there are no logs we can remove the fallback in future. Else we might need to rerun the migrations for the specific merchant connector account.
The text was updated successfully, but these errors were encountered:
The migration api can be run on the deployment environment only after the 100% deployment of the specific version of hyperswitch, because there are probabilities of merchant account being created even during the deployments. Once deployment beings the apple pay details must be read from the metadata only until the migrations are done. Hence we need a fallback here which tries to read the apple pay data from the newly added column whenever need and if it fails we just log the error and try to read the apple pay data from the metadata.
Once the migration is done we can check for the error log lines during the read form newly added column, if there are no logs we can remove the fallback in future. Else we might need to rerun the migrations for the specific merchant connector account.
The text was updated successfully, but these errors were encountered: