bcgov / bcgov/wps

ASA: Can we move away from using the FUEL_RASTER_NAME env

Open
#4,654 0 comments 0 reactions 0 assignees View on GitHub
4Refinement Task
Dominant language
Python
Stars
65
Forks
11
Avg merge
21h 25m
Merged PRs (30d)
70

Description

**Describe the task**
It would be nice if we could remove our dependence on the FUEL_RASTER_NAME environment variable.

**Acceptance Criteria**
- [ ] No more FUEL_RASTER_NAME
- [ ] All writing and reading of data works without this env
- [ ] Migrations work without this env
- [ ] Jobs work without this env

**Additional context**
- Add any other context about the task here.
- Or here

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by locating all reads and writes of FUEL_RASTER_NAME, then trace its use through data access, migrations, and jobs. Done means those areas work without the environment variable and no references remain.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.