fix(api): Warn at startup when Cloudinary settings are only partially configured

Open Beginner friendly
#677 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust

Research direction

Start in crates/api/src/state.rs and read CloudinaryConfig::from_env to see how the three settings are handled. Add tests for the configuration helper with 0, 1, 2, and 3 variables set, and run the checks named in the issue. Done means partial configuration produces one warning naming only missing variables, fully absent configuration keeps uploads disabled, and all checks pass.

Written by the indexing model from the issue text.

Description

area/backend bug good first issue help wanted

Description

CloudinaryConfig::from_env returns None if any of the three variables is missing or empty, so a half-configured server silently disables uploads and users only see a 400 later.

Requirements and context

  • Where: crates/api/src/state.rs
  • Security: Never log CLOUDINARY_API_SECRET or the key value.
  • Testing: just fmt-check, just lint and just test must pass; add or update tests for the change.
  • Documentation: Update the nearest doc if behaviour changes; otherwise no doc change is needed.

Suggested execution

  • Comment on this issue to claim it, then fork the repository and branch from main.
  • Branch name: git checkout -b fix/api-cloudinary-partial-config

Implement changes

  • Detect 'some but not all' variables set.
  • Emit one tracing::warn! naming the missing variables (never their values).
  • Keep the disabled behaviour.

Test and commit

  • Unit-test the helper with 0, 1, 2 and 3 variables set (use a small pure function over Option<String>s).
  • Run just fmt, just lint and just test locally before pushing (see CONTRIBUTING.md).
  • Commit with a conventional message and keep the change small and focused.

Example commit message

fix(api): warn on partial cloudinary config

Guidelines

  • Open the PR against main and link it with Closes #<this issue>.
  • Keep the diff focused on this issue; no unrelated refactors or formatting churn.
  • One line per comment, no bloated code; follow patterns already used in the crate.
  • Never commit secrets, .env files or real keys; use public test vectors only.
  • CI (fmt, clippy -D warnings, tests) must be green before requesting review.
  • Ask in the issue thread if anything is unclear before starting.
Dominant language
Rust
Stars
0
Forks
91
Avg merge
5h 23m
Merged PRs (30d)
4

Getting set up

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.

More from Octo-Protocol-org/Octo-Protocol

All issues in Octo-Protocol-org/Octo-Protocol

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.