-
Notifications
You must be signed in to change notification settings - Fork 17
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
AzureMLAssetDataset's credentials are not passed correctly when used in a dataset factory #160
Comments
Here's my current workaround : I create a custom Dataset :
I also have a custom hook :
After that, I ensure that my hook is loaded correctly in settings.py
For usage, it looks as follow :
After that, you should be able to do your regular |
and a bit more code for when you send the pipeline to azure :
The main issue is that for some reason, generator.py insist on using |
When used in a dataset factory, azureml's credentials are not setup correctly and creates a crash instead. For instance, the following crashes with missing credentials :
The issue is that when the catalog is created, the dataset factories are not actual datasets, but dataset_pattern, which are resolved afterward. Then the hook for after_catalog_created is called, but still no actual dataset for the dataset_pattern.
I've discussed with some people on kedro's slack channels, and they seem to agree that the best way to pass the credentials would be with a after_context_created hook.
I'll open a pull request soon to fix that, with the following pattern instead :
The text was updated successfully, but these errors were encountered: