-
Notifications
You must be signed in to change notification settings - Fork 444
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
make v2 key and v3 key configureable / check their usage #365
Comments
@grosser |
that would force all users to update their config ? |
I have been thinking about the following
But I suppose we could also do the following
I am thinking that adding version to config may not be a good idea since v3 and v2 may both be used in the same application. |
the first option sounds like a smooth transition from the unified key |
Thank you.
|
Please make a PR ... even if it's super crude at first, just so we see that
the direction makes sense :)
…On Mon, Aug 29, 2022 at 9:21 PM harata ***@***.***> wrote:
Thank you.
I would like to implement this in the first option
Add optional v2_site_key and v3_site_key to config
Use v3_site_key if argument action is present, use site_key if v3_site_key
is not set
Use v2_site_key if there is no action argument, or use the site_key if the
v2_site_key is not set
—
Reply to this email directly, view it on GitHub
<#365 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAACYZ2VGVCBLXG6FKFWZELV3WD55ANCNFSM4QPFI3OQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
see discussion in #352 and then revert it
/cc @rbarreca @SvcDptDev
The text was updated successfully, but these errors were encountered: