Hi there. Apologies for my [spamming of

[dusk spade]

When working with dagger 0.18.12 and running my demo project, I have no problems.

dagger/dagger@v0.18.12

Trace: https://dagger.cloud/nine/traces/59c4e0afbc3271db9f6eb3a5baf855cd

dagger -m github.com/dagger/dagger@v0.18.12 <<EOF
  dev |
  with-directory example \$(git https://github.com/chrisjpalmer/dagger-deps-example | head | tree) |
  with-workdir example |
  with-exec -- dagger -c 'workflow-pretend \$(secrets-manager) | doit'
EOF

However when switching to the main branch I get some issues...

dagger/dagger@main

Trace: https://dagger.cloud/nine/traces/35e514dd9cad792f2b3277754e86c908

dagger -m github.com/dagger/dagger@main <<EOF
  dev |
  with-directory example \$(git https://github.com/chrisjpalmer/dagger-deps-example | head | tree) |
  with-workdir example |
  with-exec -- dagger -c 'workflow-pretend \$(secrets-manager) | doit'
EOF

Error: instantiate: toSelectable: unknown type "SecretsManager"                                                                                                                                                   
! process "dagger -c workflow-pretend $(secrets-manager) | doit" did not complete successfully: exit code: 1

My understanding is that both should work as I feel what I am doing is supported by dagger. I am using dagger shell to inject a concrete type into another module constructor which accepts an interface parameter.

I wasn't originally concerned about testing the main branch.. I was actually testing out shykes blueprint modules branch when I discovered this issue. After some more testing, I don't think this is really linked to that branch since its reproducible from the main branch.

[foggy field]

Thanks for reporting, looking into this!

[tacit locust]

Thanks for letting us know! I am fairly certain this is the same as an issue I have been working on fixing. Only on main, not a release yet. We will fix it before the next release is done.

[tame rover]

should we create a stand-in issue? just to put into the milestone?

[foggy field]

@paper obsidian are you planning to release blueprints in a "preview" in an upcoming release, or are you still looking to get more feedback and iterate on your branch?

[paper obsidian]

The branch is merged as of today. It should be part of 0.18.3 which is imminent. There are no docs yet. We need to ship some docs + a blog post for 0.19

[paper obsidian]

Yes that definitely needs an issue... @dusk spade would you mind filing it, so we can trace it back to you in the record? 🙏 Sorry for the regression & thank you!

[foggy field]

Got it, thanks for confirming!

[tame rover]

issue at https://github.com/dagger/dagger/issues/10738

[dusk spade]

^ I will just add to this issue that already is here