BjornPrime opened a new issue, #25676:
URL: https://github.com/apache/beam/issues/25676

   ### What would you like to happen?
   
   Replace references to the apitools-generated storage client 
(sdks/python/apache_beam/io/gcp/internal/clients/storage) with analogous calls 
to the [Google Cloud Storage](https://github.com/googleapis/python-storage) 
client, supplementing with other Google Cloud Python clients if necessary.
   
   Please ensure that all client references are being thoroughly tested before 
swapping the GCS client in for the old client. The job is done when the old 
client can be safely deleted from Beam without impacting functionality.
   
   Background:
   
   apitools is deprecated and continued reliance on it is complicating Beam's 
dependency management. In order to remove it we need to replace the clients 
that it currently generates with [Google Cloud 
Python](https://github.com/googleapis/google-cloud-python) clients, which are 
being actively maintained (and should be reasonably up-to-date in google3, 
though please confirm for any particular libraries you end up using.)
   
   ### Issue Priority
   
   Priority: 2 (default / most feature requests should be filed as P2)
   
   ### 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


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to