Feature Request: Scoped AWS profile variable (`SCCACHE_AWS_PROFILE`)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.7k
- Forks
- 748
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
Currently, several object storage backends have SSCCACHE_ scoped options to control which credentials are used.
(N.B. The same applies to conf files, but talking env vars here for simplicity!)
For AWS, however, it always defaults to the standard AWS_PROFILE env vars.
I use various different profiles, but have a consistent/shared S3 bucket which one of the profiles has r/w access to, so I'd like to be able to enforce that profile is always used for sccache, even if I'm actively using a different AWS profile.
I'm happy to try and contribute a PR for this if it seems like a worthwhile change.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the AWS object-storage backend and the existing scoped SSCCACHE_ environment-variable handling. Trace how AWS_PROFILE is read, then define the expected precedence for SCCACHE_AWS_PROFILE and verify the behavior with the relevant tests or configuration coverage. Done means sccache can consistently select the requested AWS profile without changing the user's active AWS_PROFILE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, rust
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100