-
Notifications
You must be signed in to change notification settings - Fork 36
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
Use same secret key to manage different functions #97
Comments
Could you elaborate on this? I'm not sure I understand why you can't use the same API key for multiple instances of the extension? |
Of course @jasonbosco . When using the extension, you create a secret each time you define the function. If you have 5 collections, you need 5 secrets, one per collection, using the same Typesense API key. The configuration must have a way to use the previously created secret from the first function on others. |
Ah I see what you mean now. I wonder if this is a Firebase UI limitation that doesn't let you pick an existing secret? You might want to try using the Firebase CLI to install the extension and then it might allow you to reference an existing secret by its resource ID? (I'm not too familiar with this though - might be a better question for Firebase support). |
Migrating to v2 allows you to use |
May I know v2 of what package you're referring to? |
Im finding this to be a limitation when having multiple extensions for different tyepsense collections when adding the local config and deploying via the CLI. This is the error I get in the cli. Therefore I can confirm a limitation with GCP?
|
I'm referring to Cloud Functions V2. Dependencies ...
"dependencies": {
...
"express": "^4.21.2",
"firebase": "^11.0.2",
"firebase-admin": "^13.0.1",
"firebase-functions": "^6.1.1",
"typesense": "^1.8.2"
},
...
Firebase Cli firebase-tools: |
Interesting @stevebrowndotco . Could you please share the prompt you used to configure the ext? I see that this ext adds the following parameters when creating the secret key: |
To (for example)
Also trying multiple versions in the same key will not work either. |
Description
As the title implies, please allow using the same key for multiple functions. It's expensive to create the same key over and over again just to be used by 1 function.
Steps to reproduce
NA
Expected Behavior
One secret key for multiple functions.
Actual Behavior
The same key is created and used per function.
Metadata
Typesense Version: 0.27.1
OS: MacOS
The text was updated successfully, but these errors were encountered: