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

confusion around dictionary deprication #71

Open
0rphon opened this issue May 16, 2024 · 0 comments
Open

confusion around dictionary deprication #71

0rphon opened this issue May 16, 2024 · 0 comments

Comments

@0rphon
Copy link

0rphon commented May 16, 2024

fastly::dictionary is marked as deprecated with the note "renamed to config_store". This is kinda confusing to me. As far as i can tell, dictionaries and config stores are two completely different things. And you don't say anything about dictionaries being deprecated in your docs.

I'm building a service right now that requires dictionaries for some things that need to be configured on a per-service basis. Is it okay to use fastly::dictionary still? Or am i required to create a separate config store for every service?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant