🚀
ShipWithDjango Documentation
  • Welcome to ShipWithDjango Documentation
  • When and How to use ShipWithDjango?
  • Getting Started
    • Obtaining a license
    • Downloading ShipWithDjango
    • Running locally
    • Next steps
  • Platform
    • Default Configuration
    • Subnavigation
  • Theme
    • Tailwind CSS
    • Configuration
  • Secret Management
    • Default Configuration
    • Setting your environment variables
    • Third-party providers
      • Infisical
      • AWS Secrets Manager
      • Azure Key Vault
    • Order of retrieval
  • Authentication
    • Default Configuration
    • GitHub
    • LinkedIn
  • Emailing
    • Default Configuration
    • Using SendGrid
    • Using SMTP
    • Using the task queue for sending emails
  • Payments & Billing
    • Billing
    • Stripe
  • OpenAI/Dall-E
    • Default Configuration
  • API
    • Django REST framework
    • Built-in API utilities
    • Postman
  • Logging
    • Default Configuration
    • Using Sentry
    • Using Better Stack
  • Localization
    • Translations
Powered by GitBook
On this page
  1. Secret Management

Order of retrieval

The secrets manager in ShipWithDjango follows a specific order when retrieving secrets:

  1. Cache: First, it checks its cache to see if the secret has already been retrieved during the current session.

  2. Environment File: Next, it looks in the .env file. If the secret is found there, it returns that value.

  3. External Provider: If the secret is not found in the cache or the .env file, the manager will then query the configured external secret management service (Infisical, AWS, or Azure).

This layered approach allows you to easily override secrets for local development or testing by simply adding them to your .env file, while still benefiting from the security of an external provider in other environments.

PreviousAzure Key VaultNextDefault Configuration

Last updated 9 months ago