Skip to content

[ManagedIO] Single source of truth for ManagedIO configs #34720

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 16 commits into
base: master
Choose a base branch
from

Conversation

ahmedabu98
Copy link
Contributor

This creates a source of truth for ManagedIO configs, based on two yaml files under sdks/java/managed/src/main/resources/:

  1. available_configs.yaml
  2. config_aliases.yaml

(1) provides a list of available configs that should be made public, while (2) provides aliases for existing config fields.

A fleshed out Beam website page is generated according to the configuration in these two files, displaying a summary of each Managed IO's configuration as well as a more detailed view with descriptions. All of this information is pulled from individual SchemaTransforms.

@@ -688,6 +688,11 @@ project.tasks.register("generateExternalTransformsConfig") {
dependsOn(":sdks:python:generateExternalTransformsConfig")
}

// Generates the Managed IO Beam web page
project.tasks.register("generateManagedIOPage") {
dependsOn(":sdks:python:generateManagedIOPage")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we run this regularly or triggered by some tasks?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a test to the beam_PreCommit_Xlang_Generated_Transforms workflow.
The test regenerates and compares with the existing doc. If there's a mismatch, the test fails and tells the developer to run this command and commit the updates

Copy link
Contributor

Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment assign set of reviewers

@github-actions github-actions bot added the build label Apr 24, 2025
@liferoad
Copy link
Contributor

Please check the failed workflows before merging it.

@github-actions github-actions bot added the gcp label Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants