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

Separate channeldata generation into a separate process. #147

Open
2 tasks done
dholth opened this issue Apr 2, 2024 · 0 comments
Open
2 tasks done

Separate channeldata generation into a separate process. #147

dholth opened this issue Apr 2, 2024 · 0 comments
Labels
type::feature request for a new feature or capability

Comments

@dholth
Copy link
Contributor

dholth commented Apr 2, 2024

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

It should be possible to generate channeldata from an output tree by reading in all the existing */repodata.json, and combining them. Instead of having to generate them at the same time as repodata.json.

We may or may not currently save some time parsing repodata.json into channeldata by starting with the already-parsed version, but it would be nice to be able to generate the not-often-used channeldata at a different frequency than the always-used repodata.

Why is this needed?

This would give us more flexibility when generating channeldata and repodata.

What should happen?

No response

Additional Context

No response

@dholth dholth added the type::feature request for a new feature or capability label Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::feature request for a new feature or capability
Projects
Status: 🆕 New
Development

No branches or pull requests

1 participant