Skip to content

Conversation

@AlexandreOuellet
Copy link

@AlexandreOuellet AlexandreOuellet commented Oct 16, 2024

Fixing #160

Essentially, I explicitly inject the azureml's credential with after_context_created into a azureml key, then I used this key in the AzureMLAssetDataset as "credentials".

AlexandreOuellet and others added 4 commits October 16, 2024 11:54
catalog already has a __contains__ method, which ensures that the dataset name (or input/output name in some cases) fits either with a known dataset, or a dataset pattern, which enables it to work with dataset factory
@AlexandreOuellet AlexandreOuellet marked this pull request as draft October 17, 2024 18:05

catalog.add(dataset_name, dataset, replace=True)

for input in pipeline.all_inputs():
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is where the main difference happens. Instead of looping over the catalog, we loop over the pipeline's input, and then verify within the catalog if we have that input. That way, it gives a chance for the dataset factories to be instantiated, and they are then handled as usual (call as_remote(), etc...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant