Added a How-To section for VSCode debugging#1673
Added a How-To section for VSCode debugging#1673jasonviviano wants to merge 23 commits intodapr:v1.2from jasonviviano:jviviano
Conversation
| } | ||
| ``` | ||
|
|
||
| This is the full list of the parameters the Daprd tasks you need to create can use, not all are going to be necessary but for future customization its important to be aware. |
There was a problem hiding this comment.
We should add a table for:
- parameter
- Description
- Required
- Example
There was a problem hiding this comment.
@AaronCrawfis @orizohar @msfussell - We can add a new table here, or we can add a VS Code param column to this existing table and link to it: https://docs.dapr.io/reference/arguments-annotations-overview/
Thoughts?
There was a problem hiding this comment.
Created the table but do need some suggestions on exactly what an example placementHostAddress, sentryAddress and controlPlaneAddress would represent left those empty
There was a problem hiding this comment.
@AaronCrawfis @orizohar @msfussell - We can add a new table here, or we can add a VS Code param column to this existing table and link to it: https://docs.dapr.io/reference/arguments-annotations-overview/
Thoughts?
Aren't the VS Code params just daprd params? I think the daprd column should be enough
There was a problem hiding this comment.
They are, but they are formatted slightly differently so it's not a copy paste solution.
There was a problem hiding this comment.
Created the table but do need some suggestions on exactly what an example placementHostAddress, sentryAddress and controlPlaneAddress would represent left those empty
I'm not sure these are relevant to self hosting mode. Most likely these should just be a local address. Need to confirm with @artursouza or @wcs1only
There was a problem hiding this comment.
Confirmed, they're just localhost addresses. Have updated the table.
There was a problem hiding this comment.
These are localhost in case of local development.
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Mark Fussell <mfussell@microsoft.com>
…-how-to-debug-multiple-dapr-apps.md Co-authored-by: Mark Fussell <mfussell@microsoft.com>
…ons based on comments.
|
I pushed a commit with some changes to style and tone |
AaronCrawfis
left a comment
There was a problem hiding this comment.
Content looks good! I have some suggestions though that I can't paste in the GitHub UI. Could you allow maintainers to push content to your branch?
|
Actually it looks like you already did, will debug on my end |
|
See #1687 |
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Added a section to explain the usage of VS Code configurations for multiple Dapr applications.
Issue reference
#1657