New projects api #35
Merged
New projects api #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 21, 2022
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR closes the following issues:
#31
#27
#28
blocknetdx/exrproxy-env#206
blocknetdx/exrproxy-env#203
blocknetdx/exrproxy-env#204
blocknetdx/exrproxy-env#178
The behavior the Payment Processor will have after this PR is merged is described in the (freshly updated) Projects section of the API docs: https://api.blocknet.org/#projects-api-xquery-hydra
The SNode deployment docs (https://docs.blocknet.org/service-nodes/setup/#deploy-enterprise-xrouter-environment) have also been updated to reflect the changes made in this PR.
There are complementary PRs in the
exrproxyandexrproxy-envrepos of the same name which should be merged simultaneously with this one.Note: The changes in this PR have only been about 75% tested. It really should be tested by others; not just me! That said, the easiest way to make it possible for others to test these changes is to merge this to
masterso a new docker image for the Payment Processor will be built and uploaded as thelatestimage on docker hub. This is obviously not good standard practice, but should be fine atm considering there are exactly ZERO people currently using the Payment Processor.