Open-EO / Open-EO/openeo-python-driver

eliminate hardcoded openEO Platform and terrascope ToS/PP links

Open
#431 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue technical debt
Dominant language
Python
Stars
12
Forks
8
Avg merge
6d 3h
Merged PRs (30d)
4

Description

These are hardcoded links in capabilities doc:

https://github.com/Open-EO/openeo-python-driver/blob/4d9d8b1d689a62b60d819459559bd5faf35650b6/openeo_driver/views.py#L458-L465

should be moved to deployment-specific configs

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in openeo_driver/views.py at lines 458-465 and trace how the capabilities document is assembled. Identify the deployment-specific configuration entry points used there, then verify that the capabilities output takes the Terms of Service and Privacy Policy links from configuration rather than fixed URLs.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend-api-design
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.