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

Let Layotto support Dapr's Config API (alpha version) #347

Closed
seeflood opened this issue Dec 1, 2021 · 3 comments
Closed

Let Layotto support Dapr's Config API (alpha version) #347

seeflood opened this issue Dec 1, 2021 · 3 comments
Assignees
Labels

Comments

@seeflood
Copy link
Member

seeflood commented Dec 1, 2021

What would you like to be added:
Let Layotto support Dapr's Config API (alpha version)

We have been discussing and working with Alibaba and Dapr community to contribute a Config API for Dapr since March of this year,and recently it was finally merged into Dapr .
Now it's time to can make Layotto support Dapr's Config API.
Dapr Config API is still in the alpha version, which is similar to Layotto's existing Config API but lacks some fields. You can refer to Layotto's existing implementation during development.
See Dapr's API definition

Why is this needed:
To build a standard for runtime API

@github-actions
Copy link

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

@github-actions github-actions bot added the stale label Jan 17, 2022
@github-actions
Copy link

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 or help wanted. Thank you for your contributions.

@seeflood seeflood reopened this Jan 25, 2022
@github-actions
Copy link

github-actions bot commented Feb 2, 2022

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 or help wanted. Thank you for your contributions.

@github-actions github-actions bot closed this as completed Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants