forked from hyperledger/firefly
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Enterprise fork update from HL - Sep 28 2023 #89
Merged
Merged
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
Member
peterbroadhurst
commented
Sep 28, 2023
•
edited
Loading
edited
- Replace token pool "confirmed" state with "active" bool hyperledger/firefly#1305
- Enhance OpenAPI interface, for namespace-local APIs, and extra routing options hyperledger/firefly#1400
- Update README.md hyperledger/firefly#1399
- Fix SQL migration conflict and coverage gaps hyperledger/firefly#1401
- Tezos plugin support hyperledger/firefly#1402
- Update manifest hyperledger/firefly#1403
- check enabled for organization creation in non-multiparty system hyperledger/firefly#1405
- Fix table of contents view hyperledger/firefly#1409
- Fix database migration order hyperledger/firefly#1407
- Handle idempotent retry after error during initializing phase hyperledger/firefly#1406
Token pool states were originally given similar names to message state, but this has ended up being confusing (because the token pool creation flow includes a message, but the token pool states have no relation to the identically named message states). Old terminology: When pool definition message is "confirmed", pool is created as "pending" When pool gets "activated" by the connector, pool is moved to "confirmed" New terminology: When pool definition message is "confirmed", pool is created as "not active" When pool gets "activated" by the connector, pool is moved to "active" My hope is that the new terminology is easier to follow, since it does not overlap with messaging states and more clearly denotes the action of "activating" a token pool. Signed-off-by: Andrew Richardson <andrew.richardson@kaleido.io>
Add OpenSSF Best Practices badge Signed-off-by: Nicko Guyer <nguyer@users.noreply.github.com>
Replace token pool "confirmed" state with "active" bool
…ents Enhance OpenAPI interface, for namespace-local APIs, and extra routing options
Update README.md
Signed-off-by: Nicko Guyer <nicko.guyer@kaleido.io>
Signed-off-by: Nicko Guyer <nicko.guyer@kaleido.io>
Fix SQL migration conflict and coverage gaps
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Tezos plugin support
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Update manifest
Signed-off-by: Arindam Dasgupta <arinddas@in.ibm.com>
…ization creation in non-multiparty system Signed-off-by: Arindam Dasgupta <arinddas@in.ibm.com>
…rganization check enabled for organization creation in non-multiparty system
…pPhase enum Signed-off-by: Peter Broadhurst <peter.broadhurst@kaleido.io>
Signed-off-by: Nicko Guyer <nicko.guyer@kaleido.io>
Signed-off-by: Dzianis Andreyenka <andreenkodn@gmail.com>
Fix table of contents view
Fix database migration order
…r creating the TX Signed-off-by: Peter Broadhurst <peter.broadhurst@kaleido.io>
Signed-off-by: Peter Broadhurst <peter.broadhurst@kaleido.io>
Handle idempotent retry after error during initializing phase
alexwood
approved these changes
Sep 29, 2023
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.