Skip to content
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

feat: Ensure async workflow executions have access to shared container #8157

Merged
merged 2 commits into from
Jul 17, 2024

Conversation

sradevski
Copy link
Member

@sradevski sradevski commented Jul 17, 2024

REF FRMW-2595

Copy link

vercel bot commented Jul 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
api-reference 🔄 Building (Inspect) Visit Preview 💬 Add feedback Jul 17, 2024 9:52am
medusa-dashboard ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 17, 2024 9:52am
5 Skipped Deployments
Name Status Preview Comments Updated (UTC)
api-reference-v2 ⬜️ Ignored (Inspect) Visit Preview Jul 17, 2024 9:52am
docs-ui ⬜️ Ignored (Inspect) Visit Preview Jul 17, 2024 9:52am
docs-v2 ⬜️ Ignored (Inspect) Visit Preview Jul 17, 2024 9:52am
medusa-docs ⬜️ Ignored (Inspect) Visit Preview Jul 17, 2024 9:52am
resources-docs ⬜️ Ignored (Inspect) Visit Preview Jul 17, 2024 9:52am

Copy link

changeset-bot bot commented Jul 17, 2024

⚠️ No Changeset found

Latest commit: f41dde9

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

@olivermrbl olivermrbl left a comment

Choose a reason for hiding this comment

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

Overall LGTM, but I'll leave the approval to Carlos and Adrien. I just had one thought, that I'd like your thoughts on

@sradevski sradevski marked this pull request as ready for review July 17, 2024 09:14
@sradevski sradevski force-pushed the fix/pass-shared-container-workflows branch from ef1f118 to 5f374a4 Compare July 17, 2024 09:14
@sradevski sradevski requested a review from a team as a code owner July 17, 2024 09:14
@sradevski sradevski force-pushed the fix/pass-shared-container-workflows branch from 31ae462 to f41dde9 Compare July 17, 2024 09:50
@sradevski sradevski merged commit 26d600b into develop Jul 17, 2024
23 checks passed
Copy link
Member

@adrien2p adrien2p left a comment

Choose a reason for hiding this comment

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

Sorry for the delay, just had time to review it now. It looks very good to me, just one thing, can we now omit or make optional the container to be provided when calling the run from the workflow engine public api?

@adrien2p
Copy link
Member

Cc @shahednasser we are not obliged anymore to provide the container when using the workflow engine, which is a first step to later not have to pass the container to workflow either (still need some work such as using the workflow engine if provided to run the workflows under the hood)

@shahednasser
Copy link
Member

@adrien2p got it, I think once we have the second step (not having to pass the container to a workflow) we can update the docs to just be helloWorkflow.run rather than helloWorkflow(container).run

@sradevski sradevski deleted the fix/pass-shared-container-workflows branch July 17, 2024 10:35
@sradevski
Copy link
Member Author

@adrien2p #8165

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

Successfully merging this pull request may close these issues.

5 participants