separate out state directory from project directory
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 2
Description
for opensource projects builtin on chalice it would be useful to be able to specify a separate state directory then a subdirectory of the source.
the current model of chalice where configuration/state lives alongside the source makes distribution and reuse of apps problematic. either the state is set to vcs ignore, in which case state never gets versioned or state gets checked in, in which case its introducing extraneous drift from the project repo.
the goal here would be to enable distribution of chalice apps through pip as well having clean vcs repos that others can checkout and use.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Begin by locating where Chalice stores configuration and state, then verify that an app distributed through pip can use a separate state directory while the source repository remains clean.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100