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

[CLI] search option #6

Open
jbolda opened this issue Aug 4, 2020 · 1 comment
Open

[CLI] search option #6

jbolda opened this issue Aug 4, 2020 · 1 comment

Comments

@jbolda
Copy link

jbolda commented Aug 4, 2020

Each time we run a unique hash is created so we have no way to tell if a particular tag has been published yet. Being able to consistently publish every tag for a release means that we need to be able to recover from a failure in the process.

If we have a search option (that can have a time element to it to limit the scope of search), we can search and check for a transaction. If it already exists, then we know we can skip publishing that particular tag. This would let us retry as needed without creating unnecessary tag+hash while attempting.

@jbolda
Copy link
Author

jbolda commented Aug 10, 2020

Thinking about the time element more, it seems like an arbitrary number would still fall down (say for cases where a package is published once a quarter, what time range is "enough"?). If we specify a GitHub Release / tag, I imagine we could (optionally) use the date from that publish as the lower bounds from which to search.

@jbolda jbolda changed the title search option in CLI [CLI] search option Aug 10, 2020
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

No branches or pull requests

1 participant