validation: fix bucket name validation for GCS and Azure #1370
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When validating storage configurations, we were previously using the same regex for all types of cloud storage. But it turns out that GCS is more permissive, and Azure is more restrictive. This introduces separate regexes for each type of cloud storage provider. For custom storage endpoints, the GCS regex is used, as it's the most permissive.
github-actions bot
pushed a commit
to estuary/homebrew-flowctl
that referenced
this pull request
May 31, 2024
## What's Changed * `sum` annotation now supports arbitrary precision using string-encoded numerics * Add experimental `flowctl raw stats` sub-command * Various minor JSON Schema handling improvements. * Switch to simd-json for fast JSON parsing and transcoding. ### Filtered PRs impacting `flowctl`: * crates/json: don't validate strings with underscores as integers or numbers by @williamhbaker in estuary/flow#1364 * Update `runtime::container::start()` to take a new `allow_local` flag by @jshearer in estuary/flow#1361 * json: fix ordering of integers greater than i64::MAX by @psFried in estuary/flow#1367 * validation: fix bucket name validation for GCS and Azure by @psFried in estuary/flow#1370 * thread through `--allow-local` argument when running locally by @psFried in estuary/flow#1374 * validation: allow unsatisfiable constraints on excluded fields by @psFried in estuary/flow#1375 * update a number of dependencies, including RocksDB (to 8.10) by @jgraettinger in estuary/flow#1389 * connector-init: set connector_type on protocol check Spec by @jgraettinger in estuary/flow#1400 * models/journals: region configuration for S3 storage mappings by @williamhbaker in estuary/flow#1410 * improve schema validation errors by including metadata about the collection that failed by @jgraettinger in estuary/flow#1408 * flowctl: resurrect stats subcommand under raw by @psFried in estuary/flow#1432 * make: codesign binaries on mac by @mdibaiee in estuary/flow#1436 * simd-doc, gazette, avro, and dekaf crates by @jgraettinger in estuary/flow#1448 * flowctl(preview): multiple bindings may read from one collection by @mdibaiee in estuary/flow#1466 * crates/doc: support arbitrary precision with `sum` annotation by @jgraettinger in estuary/flow#1477 * crates/doc: relax `sum` inspection to allow numeric strings by @jgraettinger in estuary/flow#1481 **Full Changelog**: estuary/flow@v0.3.12...v0.3.13
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When validating storage configurations, we were previously using the same regex for all types of cloud storage. But it turns out that GCS is more permissive, and Azure is more restrictive. This introduces separate regexes for each type of cloud storage provider. For custom storage endpoints, the GCS regex is used, as it's the most permissive.
This change is