sorry-cypress
  • Documentation
  • Guide
    • Get Started
    • Dashboard and API
    • Cloud Setup
  • Cloud
    • AWS
      • Basic AWS Setup
      • Advanced AWS Setup
      • AWS Networking
      • AWS S3 Manual Setup
    • Google Cloud
      • Google Cloud & MinIO - Deprecated
    • Microsoft Azure
    • Heroku
    • Kubernetes
    • Docker Images
  • Integrating Cypress
    • Integration options
    • cy2 - Deprecated
    • Agent Configuration - Deprecated
    • CLI One Liners - Deprecated
  • Configuration
    • Basic Setup
    • Full Setup
    • Director Service
      • AWS Role Assumption via Service Account
      • AWS S3 Configuration
      • Minio Configuration
      • Azure Blob Storage Configuration
    • API Service
    • Web Dashboard
      • Configuration
    • MongoDB Configuration
    • Troubleshooting
  • Integrations
    • Events
    • Webhooks
    • Slack Integration
    • GitHub Integration
    • BitBucket Integration
    • MS Teams Integration
  • Concepts
    • Parallelization Explained
    • Flaky Tests
    • Test Details
    • Test Status
  • CI
    • GitHub Actions
    • Travis
    • Jenkins
    • AWS Codebuild
  • Development
    • Changelog
    • Development Guide
  • Community Content
  • ❤️ Contributions
  • Support
  • Legal
  • FAQ
Powered by GitBook
On this page
Edit on GitHub
  1. Configuration
  2. Director Service

Azure Blob Storage Configuration

Azure Blob Storage and Sorry Cypress

PreviousMinio ConfigurationNextAPI Service

Last updated 2 years ago

is the object storage solution provided by Microsoft, like S3 is provided by AWS.

Sorry Cypress can use an Azure Blob Storage container in order to stores the screenshots and videos taken during tests.

In order to use minio as storage driver provider, you need to configure director service

SCREENSHOTS_DRIVER="../screenshots/azure-blob-storage.driver"

You also need to patch the cypress runner code using . The package will modify the runner code called when uploading a file in order to add specific headers needed by Azure Blob Storage.

Please note that the implementation of Azure Blob Storage uses signed URLs for both writing and reading operations. This means that your container does not need to be public. It also means that both type of URLs will expire. Signed URLs used for writing will expire after the time set using AZURE_UPLOAD_URL_EXPIRY_IN_HOURS (defaults to a day). Signed URLs used for reading will expire after a year, which is the maximum duration.

Configuration Options

Treat your connexion string as a secret and hide it.

Refer tofor setup example.

AZURE_CONNEXION_STRING="*********"

Connexion string to your Azure Blob Storage Account (documentation )

AZURE_UPLOAD_URL_EXPIRY_IN_HOURS="24"

Duration during which the signed upload urls stay valid.

AZURE_CONTAINER_NAME="sorry-cypress"

Container name for storing generated artifacts. Please make sure that the container is created and configured properly before using it.

Azure Blob Storage has the same caveats as : the hostname is part of the signed URL. Please see the Minio documentation to understand the implications in terms of network configuration.

Azure Blob Storage
cy2-azure
docker-compose.azure-blob-storage.yml
here
MinIO