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

Switch default name resolver to SQLite for local DX #1379

Closed
ItalyPaleAle opened this issue Jan 31, 2024 · 9 comments
Closed

Switch default name resolver to SQLite for local DX #1379

ItalyPaleAle opened this issue Jan 31, 2024 · 9 comments
Labels
kind/proposal A new proposal to be considered stale

Comments

@ItalyPaleAle
Copy link
Contributor

Describe the proposal

Dapr 1.13 is introducing the SQLite name resolver. We should make that the default one for the local development experience, replacing mDNS.

In fact, the mDNS resolver has various issues, including the fact that it cannot be used in many corporate environments due to network rules.

This change would only apply to the development experience.

Release Note

RELEASE NOTE: UPDATE Change default name resolver for development to SQLite

@ItalyPaleAle ItalyPaleAle added the kind/proposal A new proposal to be considered label Jan 31, 2024
@dapr-bot
Copy link
Collaborator

dapr-bot commented Mar 1, 2024

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Mar 1, 2024
@ItalyPaleAle
Copy link
Contributor Author

keep-alive

@dapr-bot dapr-bot removed the stale label Mar 1, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added stale and removed stale labels Mar 31, 2024
@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added stale and removed stale labels Apr 30, 2024
@ItalyPaleAle
Copy link
Contributor Author

keep-alive

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added stale and removed stale labels May 30, 2024
@ItalyPaleAle
Copy link
Contributor Author

👋

@dapr-bot
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

@dapr-bot dapr-bot added the stale label Jun 30, 2024
@dapr-bot
Copy link
Collaborator

dapr-bot commented Jul 7, 2024

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.

@dapr-bot dapr-bot closed this as completed Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/proposal A new proposal to be considered stale
Projects
None yet
Development

No branches or pull requests

2 participants