go-sdk: Fix execution API URL config key to use nested format #60916
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The bundle plugin was using viper key 'execution-api-url' but the config file uses nested YAML format 'execution.api_url' matching the pattern used by other config sections (edge.api_url, api_auth.secret_key). This caused the plugin to fail silently when execution.api_url was set in go-sdk.yaml because viper couldn't find the incorrectly-named key. Also fixes README.md to use YAML syntax instead of TOML.
kaxil
approved these changes
Jan 22, 2026
amoghrajesh
approved these changes
Jan 22, 2026
suii2210
pushed a commit
to suii2210/airflow
that referenced
this pull request
Jan 26, 2026
The bundle plugin was using viper key 'execution-api-url' but the config file uses nested YAML format 'execution.api_url' matching the pattern used by other config sections (edge.api_url, api_auth.secret_key). This caused the plugin to fail silently when execution.api_url was set in go-sdk.yaml because viper couldn't find the incorrectly-named key. Also fixes README.md to use YAML syntax instead of TOML.
shreyas-dev
pushed a commit
to shreyas-dev/airflow
that referenced
this pull request
Jan 29, 2026
The bundle plugin was using viper key 'execution-api-url' but the config file uses nested YAML format 'execution.api_url' matching the pattern used by other config sections (edge.api_url, api_auth.secret_key). This caused the plugin to fail silently when execution.api_url was set in go-sdk.yaml because viper couldn't find the incorrectly-named key. Also fixes README.md to use YAML syntax instead of TOML.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Found this issue when I was playing with
go-sdkfor some inspirations)The bundle plugin was using viper key
'execution-api-url'but the config file (go-sdk.yaml) uses nested YAML format'execution.api_url'matching the pattern used by other config sections (edge.api_url,api_auth.secret_key).This caused the plugin to fail silently when
execution.api_urlwas set ingo-sdk.yamlbecause viper couldn't find the incorrectly-named key (I had to add a lineexecution-api-url: xxxingo-sdk.yamlas a workaround).This PR fixes this issue. Also fixed the
README.mdto use YAML syntax instead of TOML (the doc mentioned it should be a YAML).Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.