Skip to content
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

Kedro catalog resolve cannot handle non-default environment #4238

Closed
dfossl opened this issue Oct 17, 2024 · 2 comments
Closed

Kedro catalog resolve cannot handle non-default environment #4238

dfossl opened this issue Oct 17, 2024 · 2 comments
Labels
Community Issue/PR opened by the open-source community support: needs more info

Comments

@dfossl
Copy link

dfossl commented Oct 17, 2024

Description

kedro catalog resolve provides an optional parameter to set environment. However, it assumes that the provided environment will have a "credentials" pattern. But, by default the "credentials" pattern is only found in the "local" environment.

Context

In current state kedro catalog resolve cli command cannot handle environments that aren't local OR do not have a dummy credentials in them. The expectation is that if provided an environment that the resolved data catalog entries should be provided for that environment.

Steps to Reproduce

  1. create default example kedro project
  2. kedro catalog resolve -e base

Expected Result

Command should run successfully and return resolved data catalog.

Actual Result

MissingConfigException: No files of YAML or JSON format found in C:\Users\username\Projects\error_example\conf\base or C:\Users\username\Projects\error_example\conf\base matching the glob
pattern(s): ['credentials*', 'credentials*/**', '**/credentials*']

Comments

This appears to be from unexpected behavior from the command context.config_loader.get("credentials", None) located at line 245 in kedro/framework/cli/catalog.py (see below).
image
I assume the expected behavior here would be to return None. This is likely also expected behavior from the try-except at line 36 of kedro/config/abstract_config.py (see below).
image
It appears though that the exception raised is a MissingConfigException and therefore isn't catched. kedro/config/omegaconf_config.py:251 (see below).
image

Your Environment

  • Kedro Version: 0.19.8
  • Python Version: 3.10.4
  • Windows: 10.0.17763.0
@ankatiyar ankatiyar added the Issue: Bug Report 🐞 Bug that needs to be fixed label Oct 18, 2024
@astrojuanlu astrojuanlu added Community Issue/PR opened by the open-source community and removed Issue: Bug Report 🐞 Bug that needs to be fixed labels Nov 18, 2024
@merelcht
Copy link
Member

Hi @dfossl, thanks for reporting this issue. It seems to have been a problem in Kedro 0.19.8. I've tried to reproduce your issue with the latest release and the command runs without issues. Can you try updating to Kedro 0.19.10?

Copy link

github-actions bot commented Jan 8, 2025

This issue has been closed due to lack of information. Feel free to re-open this issue if you're facing a similar problem. Please provide as much information as possible so we can help resolve your issue.

@github-actions github-actions bot closed this as completed Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community Issue/PR opened by the open-source community support: needs more info
Projects
None yet
Development

No branches or pull requests

4 participants