CsvPath Framework
  • CsvPath
  • DATA PREBOARDING
  • Getting Started
    • Quickstart
    • Your First Validation, The Lazy Way
    • Your First Validation, The Easy Way
    • Your First Validation, The Hard Way
    • DataOps Integrations
      • Getting Started with CsvPath + OpenTelemetry
      • Getting Started with CsvPath + SFTPPlus
        • SFTPPlus Implementation Checklist
      • Getting Started With CsvPath + OpenLineage
      • Getting Started with CsvPath + CKAN
    • A Helping Hand
  • Topics
    • The CLI
    • How-tos
      • How-to videos
      • Storage backend how-tos
        • Store source data and/or named-paths and/or the archive in AWS S3
        • Loading files from S3, SFTP, or Azure
        • Add a file by https
        • Store source data and/or named-paths and/or the archive in Azure
        • Store source data and/or named-paths and/or the archive in Google Cloud Storage
      • CsvPath in AWS Lambda
      • Another Example, Part 1
      • Another Example, Part 2
      • Setup notifications to Slack
      • Send run events to Sqlite
      • Sending results by SFTP
      • Working with error messages
      • Sending results to CKAN
      • Transfer a file out of CsvPath
      • File references and rewind/replay how-tos
        • Replay Using References
        • Doing rewind / replay, part 1
        • Doing rewind / replay, part 2
        • Referring to named-file versions
      • Config Setup
      • Debugging Your CsvPaths
      • Creating a derived file
      • Run CsvPath on Jenkins
    • High-level Topics
      • Why CsvPath?
      • CsvPath Use Cases
      • Paths To Production
      • Solution Storming
    • Validation
      • Schemas Or Rules?
      • Well-formed, Valid, Canonical, and Correct
      • Validation Strategies
    • Python
      • Python vs. CsvPath
      • Python Starters
    • Product Comparisons
      • The Data Preboarding Comparison Worksheet
    • Data, Validation Files, and Storage
      • Named Files and Paths
      • Where Do I Find Results?
      • Storage Backends
      • File Management
    • Language Basics
    • A CsvPath Cheatsheet
    • The Collect, Store, Validate Pattern
    • The Modes
    • The Reference Data Types
    • Manifests and Metadata
    • Serial Or Breadth-first Runs?
    • Namespacing With the Archive
    • Glossary
Powered by GitBook
On this page
  1. Topics
  2. How-tos
  3. Storage backend how-tos

Store source data and/or named-paths and/or the archive in Google Cloud Storage

Trusted publishing using Azure blobs is really quite straightforward.

PreviousStore source data and/or named-paths and/or the archive in AzureNextCsvPath in AWS Lambda

Last updated 17 days ago

This page is really just here to point to the S3 instructions because everything is basically the same.

You need a GCS_CREDENTIALS_PATH environment variable. It points to the location of your service account JSON credentials file. Other than that, there's no additional setup — just use of gs:// instead of sftp:// or s3:// in config/config.ini or when you add content with FileManager or PathsManager.

Super easy!

A screenshot of the Azure Storage Explorer app showing CsvPath Framework CSV and JSON files