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(quickstart): override Redis dependency instead of yaml edit #679

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

brooksmtownsend
Copy link
Member

Feature or Problem

This PR uses interface level overrides to override the keyvalue dependency in the quickstart.

Will depend on wash 0.37 being released, and a newer keyvalue provider version.

Related Issues

Release Information

Consumer Impact

Testing

Unit Test(s)

Acceptance or Integration

Manual Verification

Copy link

netlify bot commented Nov 1, 2024

Deploy Preview for dreamy-golick-5f201e ready!

Name Link
🔨 Latest commit 0735367
🔍 Latest deploy log https://app.netlify.com/sites/dreamy-golick-5f201e/deploys/67291536534c5d00082499b2
😎 Deploy Preview https://deploy-preview-679--dreamy-golick-5f201e.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@brooksmtownsend brooksmtownsend force-pushed the feat/interface-override-quickstart branch from 8d9044d to 0735367 Compare November 4, 2024 18:40

Check the status of the app:
Once you save `wasmcloud.toml`, we can start our developer loop up again. We'll take a look at the actual change this made to how `wash dev` generated your application later in the tutorial, so we can also output that application manifest to the current directory for later inspection.
Copy link
Contributor

Choose a reason for hiding this comment

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

This paragraph reads a little awkward to me. Suggestions @ericgregory ?


Check the status of the app:
Once you save `wasmcloud.toml`, we can start our developer loop up again. We'll take a look at the actual change this made to how `wash dev` generated your application later in the tutorial, so we can also output that application manifest to the current directory for later inspection.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Once you save `wasmcloud.toml`, we can start our developer loop up again. We'll take a look at the actual change this made to how `wash dev` generated your application later in the tutorial, so we can also output that application manifest to the current directory for later inspection.
After saving `wasmcloud.toml`, we'll start our developer loop again. This time, we'll use the `--manifest-output-dir` flag to generate an application manifest in the current directory. (We'll take a look at that file later in the tutorial.)

```shell
wash app delete hello-world
```
## The Application Manifest
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
## The Application Manifest
## The application manifest

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.

3 participants