There are legitimate reasons to require a resource on a solid, but not access it inside the solid:
- The incoming dagster mlflow resource invokes some mlflow APIs that start an mlflow run and modify global state to point to it, and then the body of the solid can log to that run by just invoking direct APIs on the mlflow package.
- step launchers