damccorm commented on code in PR #37377:
URL: https://github.com/apache/beam/pull/37377#discussion_r3150003494


##########
sdks/python/apache_beam/runners/dataflow/internal/clients/dataflow/dataflow_v1b3_messages.py:
##########
@@ -8047,11 +8062,3 @@ class WriteInstruction(_messages.Message):
     StandardQueryParameters.FXgafvValueValuesEnum, '_1', '1')
 encoding.AddCustomJsonEnumMapping(
     StandardQueryParameters.FXgafvValueValuesEnum, '_2', '2')
-encoding.AddCustomJsonFieldMapping(
-    DataflowProjectsLocationsTemplatesLaunchRequest, 
'dynamicTemplate_gcsPath', 'dynamicTemplate.gcsPath')
-encoding.AddCustomJsonFieldMapping(
-    DataflowProjectsLocationsTemplatesLaunchRequest, 
'dynamicTemplate_stagingLocation', 'dynamicTemplate.stagingLocation')
-encoding.AddCustomJsonFieldMapping(
-    DataflowProjectsTemplatesLaunchRequest, 'dynamicTemplate_gcsPath', 
'dynamicTemplate.gcsPath')
-encoding.AddCustomJsonFieldMapping(
-    DataflowProjectsTemplatesLaunchRequest, 'dynamicTemplate_stagingLocation', 
'dynamicTemplate.stagingLocation')

Review Comment:
   I think this is deleted because of a merge issue (this was added after the 
commit you're generating from) - could you try pulling in the latest contents 
of master (`git pull origin master`) and then regenerating this client?



##########
sdks/go.mod:
##########
@@ -25,12 +25,12 @@ go 1.26.0
 toolchain go1.26.2
 
 require (
-       cloud.google.com/go/bigquery v1.72.0
-       cloud.google.com/go/bigtable v1.41.0
-       cloud.google.com/go/datastore v1.21.0
+       cloud.google.com/go/bigquery v1.74.0
+       cloud.google.com/go/bigtable v1.42.0
+       cloud.google.com/go/datastore v1.22.0

Review Comment:
   Oh, and could you also mention the pipeline options in 
https://github.com/apache/beam/blob/master/CHANGES.md ? (you don't need to call 
out the client libraries there)



-- 
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