Lock file added but not used
What is the current bug behavior?
What is happening now?
Using the new MELTANO_FF_LOCK_FILES for lock files, I was able to see lock files installed into the plugins directory but when I execute the plugin it seems like that definition isnt being used by default.
It seems like the lock file is either not found so the discovery.yml is used or maybe theres a bug where the default behavior is still to use the discovery.yml.
What is the expected correct behavior?
What should be happening?
I would expect the lock file to be used over the discovery.yml definition if its present in the project.
Steps to reproduce
How one can reproduce the issue?
meltano --version
# meltano, version 1.104.0
export MELTANO_FF_LOCK_FILES=1
meltano add extractor tap-slack
# List the settings that come default
meltano config tap-slack list
# Edit the lock file to add a new setting called "foo" with kind = password
# List again and see that "foo" setting isnt listed
meltano config tap-slack list
# Set "foo" config - it gets added to meltano.yml file instead of the .env
meltano config tap-slack set foo abcRelevant logs and/or screenshots
Please use code blocks (```) to format console output
Possible fixes
If you can, link to the line of code that might be responsible for the problem or suggest a fix
Further regression test
Ensure we automatically catch similar issues in the future
-
Write additional adequate test cases and submit test results -
Test results should be reviewed by a person from the team