[Failing Test]: Pipeline Options Validator test of GCS path not compatible with new GCS client
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
### What happened?
The apitools-generated StorageV1 client has been replaced with the [GCS client](https://github.com/googleapis/python-storage). This has caused `test_gcs_path` in `pipeline_options_validator_test.py` to start failing. The reason given is that the example project (named "example:example") doesn't exist, leading to a 400 response. It couldn't be immediately established why such an issue was only affecting this test, and not the others in the file, which also seem to use boilerplate or placeholder project names.
### Issue Failure
Failure: Test is continually failing
### Issue Priority
Priority: 2 (backlog / disabled test but we think the product is healthy)
### Issue Components
- [x] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [ ] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
Contributor guide
Assessment
This issue has not been assessed yet.