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

Apollo是否可以支持按照key维度来发布? #5127

Open
hezhaoye opened this issue Apr 16, 2024 · 3 comments
Open

Apollo是否可以支持按照key维度来发布? #5127

hezhaoye opened this issue Apr 16, 2024 · 3 comments
Labels

Comments

@hezhaoye
Copy link

Apollo是否可以支持按照key维度来发布?

Copy link

dosubot bot commented Apr 16, 2024

Apollo supports releasing configurations by key dimension through the ReleaseKeyGenerator class, which generates a unique release key for each namespace based on appId, cluster, and namespace. This mechanism ensures that releases can be uniquely identified and managed. For more details, you can refer to the ReleaseKeyGenerator class in the Apollo codebase here.

If you're looking to schedule or delay the publishing of configurations, Apollo does not provide an official solution. However, there's an ongoing discussion in the community about potential workarounds, such as using external tools like the Quartz framework or a Redis delay queue to trigger configuration publishing via Apollo's OpenAPI. You can find more about this discussion here. It's important to carefully consider these approaches, as they involve external dependencies and might require a comprehensive understanding of your deployment and operational requirements.

Sources

About Dosu

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@nobodyiam
Copy link
Member

apollo 的最小发布粒度是 namespace

Copy link

stale bot commented May 22, 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 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 22, 2024
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