Sitelet https://github.com/onlimit-study/feasibility-data/pull/243
Skip to content

docs: 馃摑 add section about API keys - #243

Open
fruvago wants to merge 2 commits into
mainfrom
docs/api-key-docs
Open

fruvago wants to merge 2 commits into
mainfrom
docs/api-key-docs

Conversation

@fruvago

@fruvago fruvago commented Sep 29, 2026

Copy link
Copy Markdown
Collaborator

Description

This adds a section about API keys. Feel free to edit.

Closes #155

Needs a medium-depth review.

Checklist

  • Ran just run-all
  • (When relevant) Ran just build-package

@fruvago fruvago self-assigned this Sep 29, 2026
@fruvago
fruvago requested a review from a team as a code owner September 29, 2026 10:13

@signekb signekb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! Some minor suggestions:

Comment thread CONTRIBUTING.md
The API keys required to download data and metadata from the various data
sources are stored as environment variables. If these are not available when the
pipeline runs, tasks that fetch data or metadata from the APIs will return an
error. For reference, the `.env.example` file lists the names of all environment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
error. For reference, the `.env.example` file lists the names of all environment
error. For reference, the [`.env.example`](https://github.com/onlimit-study/feasibility-data/blob/main/.env.example) file lists the names of all environment

Might be nice to link to it?

Comment thread CONTRIBUTING.md
Comment on lines +355 to +356
own user space. If you want to override a value from the shared file for testing
or development purposes in your personal repository clone, you can add it as an

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
own user space. If you want to override a value from the shared file for testing
or development purposes in your personal repository clone, you can add it as an
own user space. If you want to use another value for testing
or development purposes in your personal repository clone, you can add it as an

Just so it doesn't sound like an actual overwrite of the value in the shared env file.

Comment thread CONTRIBUTING.md
or development purposes in your personal repository clone, you can add it as an
environment variable in a `.env` file in the project root.

When working locally, the shared environment variables file is not available. If

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When working locally, the shared environment variables file is not available. If
When working locally (i.e., outside GenomeDK), the shared environment variable file is not available. If

Comment thread CONTRIBUTING.md

When working locally, the shared environment variables file is not available. If
you are developing against a test API or working with an API that only provides
metadata, you can add the relevant API keys to a `.env` file in the project

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
metadata, you can add the relevant API keys to a `.env` file in the project
metadata, you can add the relevant API keys to a `.env` file in your project

Comment thread CONTRIBUTING.md
Comment on lines +362 to +364
root. In general, to prevent accidentally downloading participant data locally,
API keys for live data sources containing real participant data should not be
used outside GenomeDK.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
root. In general, to prevent accidentally downloading participant data locally,
API keys for live data sources containing real participant data should not be
used outside GenomeDK.
root.
::: callout-important
In general, to prevent accidentally downloading participant data locally,
API keys for live data sources containing real participant data should not be
used outside GenomeDK.
:::

Not sure that this works as intended since this is an md file, but it is rendered on the website as well (where this seems to work fine). I would just like to emphasise this part bc it's quite important.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

Add section to contributing about using API key and env files

2 participants