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

🛠️ Init Configuration checks for clearer feedback #3

Open
vpnu opened this issue Jan 23, 2024 · 0 comments
Open

🛠️ Init Configuration checks for clearer feedback #3

vpnu opened this issue Jan 23, 2024 · 0 comments
Assignees
Labels
🛠️ backlog This issue is a planned work item

Comments

@vpnu
Copy link
Contributor

vpnu commented Jan 23, 2024

Summary

When Hutch first runs, it should sanity check (conditionally) required configuration, so that it can give helpful feedback around configuration expectations, instead of allowing misconfigured components to casually throw arcane exceptions.

Starter for 10:

  • Is a RabbitMQ connection detailed?
    • can we connect?
  • Is a Minio bucket provided if the preconfigured flag is on?
    • can we connect?
  • Is a Controller API configured (or the bypass flag is on)?
    • can we connect?
  • Is the relevant wfexs config present and correct?
    • e.g. does the working directory exist?
    • is the entrypoint file there?

Tasks

TBD

Acceptance Criteria

TBD

@beforan beforan transferred this issue from Health-Informatics-UoN/hutch-cohort-discovery Jan 25, 2024
@beforan beforan self-assigned this Jan 26, 2024
@beforan beforan changed the title Init Configuration checks 🛠️ Init Configuration checks for clearer feedback Feb 12, 2024
@beforan beforan added the 🛠️ backlog This issue is a planned work item label Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛠️ backlog This issue is a planned work item
Projects
None yet
Development

No branches or pull requests

2 participants