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

fix(mojaloop/#2536): fspiop api version negotiation not handled by transfers service #487

Conversation

mdebarros
Copy link
Member

@mdebarros mdebarros commented Oct 5, 2021

  • chore: updated dependencies
  • chore: ci-cd improvements
    • updated ci dependency cache to use the commit sha instead of the package.json checksum. this will ensure that builds never re-use stale caches going forward!
    • added release and git-release jobs to CI-CD pipeline
    • removed deploy from ci-cd pipeline
    • added standard-version dev dependency, and npm script for releases
  • fix(mojaloop/#2536): fspiop api version negotiation not handled by transfers service - FSPIOP API version negotiation not handled - Transfers-service project#2536
    • added getOptionsForFSPIOPHeaderValidation to the plugin configuration
    • added new config key for PROTOCOL_VERSIONS to default and integration configs
    • updated unit/integration tests to use v1.1 protocol
    • added DEFAULT_PROTOCOL_VERSION for backward compatibility
    • MLAPI_PROTOCOL_VERSIONS__ACCEPT__VALIDATELIST can be set as follows "[ "1", "1.1"]" and it will be parsed correctly into a object
    • Note that MLAPI_PROTOCOL_VERSIONS__ACCEPT__DEFAULT is not currently used by the ML-API-Adapter, I have not included this in the default.json, but it can be set (when implemented in future). I have also added a comment in the config.js to reflect this.
    • Added unit tests for config changes

BREAKING CHANGE: Forcing a major version change for awareness of the config changes. The LIB_RESOURCE_VERSIONS env var is now deprecated, and this is now also controlled by the PROTOCOL_VERSIONS config in the default.json. This has been done for consistency between all API services going forward and unifies the config for both inbound and outbound Protocol API validation/transformation features.

- updated ci dependency cache to use the commit sha instead of the package.json checksum. this will ensure that builds never re-use stale caches going forward!
- added release and git-release jobs to CI-CD pipeline
- removed deploy from ci-cd pipeline
@mdebarros mdebarros self-assigned this Oct 5, 2021
- removed deprecated faucet dependency (replaced by tap-spec)
- added yarn.lock to gitignore
…ansfers service

- added getOptionsForFSPIOPHeaderValidation to the plugin configuration
- added new config key for PROTOCOL_VERSIONS

BREAKING CHANGE: New config key for PROTOCOL_VERSIONS
…rc ignore list as the upgrade is breaking - will have to address this on most mojaloop projects going forward
@mdebarros mdebarros marked this pull request as ready for review October 19, 2021 12:55
elnyry-sam-k
elnyry-sam-k previously approved these changes Oct 19, 2021
…LIDATELIST

- MLAPI_PROTOCOL_VERSIONS__ACCEPT__VALIDATELIST can be set as follows "[ \"1\", \"1.1\"]" and it will be parsed correctly into a object

- Note that MLAPI_PROTOCOL_VERSIONS__ACCEPT__DEFAULT is not currently used by the ML-API-Adapter, I have not included this in the default.json, but it can be set (when implemented in future). I have also added a comment in the config.js to reflect this.

BREAKING CHANGE: Forcing a major version change for awareness of the config changes. The `LIB_RESOURCE_VERSIONS` env var is now deprecated, and this is now also controlled by the PROTOCOL_VERSIONS config in the default.json. This has been done for consistency between all API services going forward and unifies the config for both inbound and outbound Protocol API validation/transformation features.
@mdebarros mdebarros merged commit c4d6b45 into mojaloop:master Nov 5, 2021
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.

2 participants