Bug: `meltano config meltano set` should always set a value
See original GitHub issue~/Development/meltano-projects/superset-test ❯❯❯ meltano config meltano set discovery_url http://localhost:4000/discovery.yml
2022-06-04T01:36:33.566497Z [info ] Environment 'dev' is active
Meltano setting 'discovery_url' was set in `meltano_environment`: 'http://localhost:4000/discovery.yml'
Current value is still: 'https://discovery.meltano.com/discovery.yml' (from the default)
I’d expect this to store discovery_url: http://localhost:4000/discovery.yml
in meltano.yml
, but it’s nowhere to be found.
Issue Analytics
- State:
- Created a year ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Settings - Meltano Documentation
If enabled, Meltano will use the value of the project_id setting to uniquely ... The same input value always produces the same output...
Read more >Change default `meltano config` behavior to `--no-environment`
For all other settings, and just in general, I think Meltano set should have a default --global or --global=true that overrides the default...
Read more >Automatically populate newly added plugin config object in ...
An error occurred while fetching the assigned iteration of the selected issue. ... values is more appropriate, I could imagine meltano config <plugin>...
Read more >meltano - PyPI
Each config should be in a directory with the name of the loader. ... Meltano uses GitLab CI/CD to set up and maintain...
Read more >Data Stacks For Fun & Nonprofit — Part III | by Andrew Stewart
The primary data source we will use for this tutorial is from the MIT ... Setting up Meltano is a simple matter of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My guess is we have two bugs here:
The second issue, I think, is the bigger issue we should tackle. The first issue might only be affecting this particular code path and (if so) might be best resolved by not trying to infer a hierarchy at all.
As a user, if I tell Meltano to store a setting, I don’t want Meltano to second guess whether it actually needs to be set.
I’ll take a deeper look tonight and @kgpayne I might assign to you since this is a part of the codebase I know you are very familiar with.
@aaronsteers I’ve set the urgency to “Higher” here because this could be a bad bug.