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

Design: Support multi-cloud configuration #567

Open
SparkYuan opened this issue Oct 8, 2023 · 0 comments · May be fixed by #577
Open

Design: Support multi-cloud configuration #567

SparkYuan opened this issue Oct 8, 2023 · 0 comments · May be fixed by #577
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature
Milestone

Comments

@SparkYuan
Copy link
Member

What would you like to be added?

Propose a design doc about how to configure different attributes of a resource existing across multiple clouds.

Why is this needed?

Differences in configurations are inevitable for a resource that exists across multiple clouds. We have abstracted common parts of the same kind of resource that exist across multiple clouds, but the different parts are not included in our AppConfig model. They are also necessary because App dev or Platform dev needs to configure them in some scenarios.

@SparkYuan SparkYuan added the kind/feature Categorizes issue or PR as related to a new feature label Oct 8, 2023
@ffforest ffforest changed the title Design: Differences in configurations among various clouds Design: Support multi-cloud configuration Oct 9, 2023
@ffforest ffforest added this to the 0.10.0 milestone Oct 9, 2023
@ffforest ffforest linked a pull request Oct 20, 2023 that will close this issue
@adohe adohe modified the milestones: 0.10.0, v0.11.0 Jan 19, 2024
@adohe adohe modified the milestones: v0.11.0, v0.12.0 Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants