@Scout: Select all asset with the same key prefix leben/ba_provision/

To select all assets with the same key prefix, you can use the

AssetSelection.key_prefixes

method. This method allows you to specify one or more key prefixes to match against asset keys. In your case, to select all assets with the key prefix

leben/ba_provision/

, you would use the following syntax:

python
AssetSelection.key_prefixes(["leben", "ba_provision"])

This will match any asset key where the first two segments are

["leben", "ba_provision"]

. Remember that the key prefix must be provided as a list of strings representing each segment of the asset key. Please note that the actual implementation of this selection in your Dagster code will depend on the context in which you're using it, such as within a job definition or when querying assets programmatically. Dagster Docs button Asset selection syntax | Dagster Docs button accept a list of asset keys in most plac... button Recommendations for how to use asset gro... button Thank you for your feedback!

@Scout: I get the following error message: "Could not load location cicd_dagster_project to check for sensors due to the following error: dagster._core.errors.DagsterInvalidSubsetError: AssetKey(s) {AssetKey(['leben', 'ba_provision', ''])} were selected, but no AssetsDefinition objects supply these keys. Make sure all keys are spelled correctly, and all AssetsDefinitions are correctly added to the

Definitions

."

The error message you're encountering indicates that the

AssetKey

you're trying to select does not match any

AssetsDefinition

objects within your Dagster project. This could be due to a few reasons: 1. The asset key is misspelled or does not exist in the codebase. Double-check the spelling and structure of your asset key to ensure it matches the defined assets. 2. The assets with the specified key prefix have not been added to the

Definitions

object. Ensure that all assets you want to select are included in the

Definitions

that you're using. 3. There might be an issue with how the asset keys are structured or how the selection is being made. Asset keys are case-sensitive and must match exactly, including all segments of the key. To resolve this issue, you should: - Verify that the assets with the prefix

leben/ba_provision/

are defined in your Dagster project with the correct spelling and structure. - Ensure that these assets are included in the

Definitions

object that is being used to load the location or repository. - If you are using a repository or workspace YAML file, make sure that the assets are correctly referenced there and that the repository or workspace is correctly configured. If you continue to face issues, you may want to review your asset definitions and how they are being included in your Dagster project. If necessary, you can also reach out to the Dagster community or support channels for more specific guidance based on your project's setup.