robertwb commented on PR #32181: URL: https://github.com/apache/beam/pull/32181#issuecomment-2364020076
> > Now that we have flex templates, we prefer not propagating the ValueProvider boilerplate elsewhere without good reason, and advise flex templates for any template use that uses non-ValueProvider-enabled features. Is there a reason you cannot use flex templates? > > Flex templates require a Docker image to be built, which is more complex than uploading a JAR file to Google Storage. For our company, it's easier to upload the classic templates with a single Gradle task than to use the artifact registry. This is good feedback. My reading of https://cloud.google.com/dataflow/docs/guides/templates/using-flex-templates#build-template is that you don't have to build the docker image yourself, just provide the jar and other metadata (just like classic templates). Hopefully it shouldn't be too hard to package this gcloud command in a gradle task directly. -- 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]
