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.

Sign up for GitHub

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

Jump to bottom

feat(publish): create a merkle tree of all publishing transactions #63

Open
jpower432 opened this issue Sep 1, 2021 · 4 comments
Open

feat(publish): create a merkle tree of all publishing transactions #63

jpower432 opened this issue Sep 1, 2021 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Backlog

Comments

@jpower432
Copy link
Contributor

To ensure integrity of metadata stored in the disconnected environments, I want to create or use a merkle tree implementation to represent all publishing transactions.
@jpower432 jpower432 added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 1, 2021
@jpower432 jpower432 added this to To-Do in Bundle via automation Sep 1, 2021
@afflom afflom removed this from To-Do in Bundle Sep 16, 2021
@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 30, 2021
@jpower432 jpower432 added this to the Backlog milestone Dec 6, 2021
@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 5, 2022
@jpower432
Copy link
Contributor Author

/remove-lifecycle rotten

@openshift-ci openshift-ci bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 19, 2022
@jpower432
Copy link
Contributor Author

/lifecycle frozen

@openshift-ci openshift-ci bot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 20, 2022
@jpower432 jpower432 removed this from the Backlog milestone Feb 1, 2022
@jpower432 jpower432 added this to To do in Backlog via automation Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Backlog
To do
Milestone
No milestone
Development

No branches or pull requests
2 participants
@openshift-bot @jpower432