shnewto opened a new issue, #27057: URL: https://github.com/apache/beam/issues/27057
### What needs to happen? Hello! 👋 I notice that the GO SDK defines its version as `.dev` of whatever version it's on, `SdkVersion = "2.49.0.dev"` currently but it also has the `.dev` in the actual releases, i.e.`SdkVersion = "2.48.0.dev"` for the `2.48.0` release https://github.com/apache/beam/blob/425186f27dc2eef0e2e45b23cd6eeb7d01ceef20/sdks/go/pkg/beam/core/core.go#L30 (This may be a bug actually, but looking through the file's history it didn't look like un-qualified version numbers were used recently.) I bring it up because it makes things sort of tricky to use the SDK in base Dataflow Flex templates in GCP. Google says it doesn't support `.dev` version numbers in Flex templates so when Dataflow jobs are triggered, they fail because Google is looking for `2.48.0.dev` (unsupported) instead of `2.48.0`. I have a couple workarounds, one is to vendor the source code and change the `SdkVersion`. The other that seems to work is to pass `environment_config='apache/beam_go_sdk:2.48.0` to short circuit whatever's happening in the `gcr.io/dataflow-templates-base/go-template-launcher-base` image. I'd be happy to make a PR if there's an appropriate thing to change in docs or some pre-release tests? But it seems like this might just be a process thing for the next `2.49.0` release. Thanks for all the work that goes into Beam! ### Issue Priority Priority: 2 (default / most normal work should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [X] 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]
