Merge branch 'master' of https://github.com/FirebasePrivate/extensions into @salakar/feat/lerna

# Conflicts:
#	firestore-send-email/package-lock.json
#	rtdb-shorten-urls-bitly/package-lock.json
#	rtdb-translate-text/package-lock.json

Author: Salakar

.github/ISSUE_TEMPLATE/bug.md

@@ -0,0 +1,40 @@
+---
+name: ⚠️ Report a Bug
+about: Think you found a bug in an extension? Report it here.
+---
+
+<!-- DO NOT DELETE
+validate_template=true
+template_path=.github/ISSUE_TEMPLATE/bug.md
+-->
+
+### [READ] Step 1: Are you in the right place?
+
+Issues filed here should be about bugs for a **specific extension in this repository**.
+If you have a general question, need help debugging, or fall into some
+other category use one of these other channels:
+
+- For general technical questions, post a question on [StackOverflow](http://stackoverflow.com/)
+  with the firebase tag.
+- For general Firebase discussion, use the [firebase-talk](https://groups.google.com/forum/#!forum/firebase-talk)
+  google group.
+- To file a bug against the Firebase Extensions platform, or for an issue affecting multiple extensions, please reach out to
+  [Firebase support](https://firebase.google.com/support/troubleshooter/contact/) directly.
+
+### [REQUIRED] Step 2: Describe your configuration
+
+- Extension name: **\_** (`storage-resize-images`, `firestore-send-email`, etc)
+- Configuration values (redact info where appropriate):
+  - **\_**
+  - **\_**
+
+### [REQUIRED] Step 3: Describe the problem
+
+#### Steps to reproduce:
+
+What happened? How can we make the problem occur?
+This could be a description, [log/console output](https://firebase.google.com/docs/extensions/manage-installed-extensions#view-logs), etc.
+
+##### Expected result
+
+##### Actual result

.github/ISSUE_TEMPLATE/fr.md

@@ -0,0 +1,26 @@
+---
+name: 💡 Feature Request
+about: Have a feature you'd like to see in an extension? Request it here.
+---
+
+<!-- DO NOT DELETE
+validate_template=true
+template_path=.github/ISSUE_TEMPLATE/fr.md
+-->
+
+### [READ] Step 1: Are you in the right place?
+
+Issues filed here should be about a feature request for a **specific extension in this repository**. To file a feature request that affects multiple extensions or the Firebase Extensions platform, please reach out to
+[Firebase support](https://firebase.google.com/support/troubleshooter/report/features/) directly.
+
+### [REQUIRED] Step 2: Extension name
+
+This feature request is for extension: **\_** (`storage-resize-images`, `firestore-send-email`, etc)
+
+### What feature would you like to see?
+
+Describe the feature you would like to add, or how you'd like to see the extension change.
+
+### How would you use it?
+
+Tell us how you'd use this feature in your app.

README.md

@@ -1,11 +1,11 @@
-# Firebase Mods
+# Firebase Extensions
 
-This repository contains the source for Firebase Mods. Created and tested by Firebase, these official Firebase mods are reliable and secure. To learn more about Firebase Mods, including how to install them in your Firebase projects, visit the [Firebase documentation](https://firebase.google.com/docs/mods).
+This repository contains the source for Firebase Extensions. Created and tested by Firebase, these official Firebase extensions are reliable and secure. To learn more about Firebase Extensions, including how to install them in your Firebase projects, visit the [Firebase documentation](https://firebase.google.com/docs/extensions).
 
-Each directory in this repo contains the source code for a mod and a README to explain how the mod works, including information about the APIs enabled, resources created, and the access granted to the mod.
+Each directory in this repo contains the source code for the extension and a README to explain how the extension works, including information about the APIs enabled, resources created, and the access granted to the extension.
 
-When you find a mod that solves a need for your app or project, all you do is install and configure the mod. With mods, you don't spend time researching, writing, and debugging the code that implements functionality or automates a task for your app or project.
+When you find an extension that solves a need for your app or project, all you do is install and configure the extension. With extensions, you don't spend time researching, writing, and debugging the code that implements functionality or automates a task for your app or project.
 
-You can also browse official Firebase mods from the following sources:
-* [Firebase Mods product page](https://firebase.google.com/products/mods)
-* [Firebase Mods dashboard](https://console.firebase.google.com/project/_/mods/) in the Firebase console
+You can also browse official Firebase extensions from the following sources:
+* [Firebase Extensions product page](https://firebase.google.com/products/extensions)
+* [Firebase Extensions dashboard](https://console.firebase.google.com/project/_/extensions/) in the Firebase console

auth-mailchimp-sync/PREINSTALL.md

@@ -15,6 +15,7 @@ You must also have a Mailchimp account before installing this extension.
 #### Billing
 
 This extension uses other Firebase or Google Cloud Platform services which may have associated charges:
+
 - Firebase Realtime Database
 - Cloud Functions
 

auth-mailchimp-sync/README.md

@@ -14,7 +14,7 @@
 
 * Audience ID: What is the Mailchimp Audience ID to which you want to subscribe new users? To find your Audience ID: visit https://admin.mailchimp.com/lists, click on the desired audience or create a new audience, then select **Settings**. Look for **Audience ID** (for example, `27735fc60a`).
 
-* Contact status: When a new contact is added to the Mailchimp list/audience, what is their initial status? If the status is `subscribed` the contact can immediately receive campaigns. If the status is `pending`, a double opt-in confirmation email will be sent to the user. Once accepted they will be set to a `subscribed` status.
+* Contact status: When the extension adds a new user to the Mailchimp audience, what is their initial status? This value can be `subscribed` or `pending`. `subscribed` means the user can receive campaigns; `pending` means the user still needs to opt-in to receive campaigns.
 
 
 
@@ -34,13 +34,13 @@ This extension adds the email address of each new user to your specified Mailchi
 
 This extension uses Mailchimp, so you'll need to supply your Mailchimp API Key and Audience ID when installing this extension.
 
-### Additional setup
+#### Additional setup
 
 Make sure that you've set up [Firebase Authentication](https://firebase.google.com/docs/auth) to manage your users.
 
 You must also have a Mailchimp account before installing this extension.
 
-### Billing
+#### Billing
 
 This extension uses other Firebase or Google Cloud Platform services which may have associated charges:
 

delete-user-data/PREINSTALL.md

@@ -15,6 +15,7 @@ Also, make sure that you've set up [Firebase Authentication](https://firebase.go
 #### Billing
 
 This extension uses other Firebase or Google Cloud Platform services which may have associated charges:
+
 - Cloud Firestore
 - Firebase Realtime Database
 - Cloud Storage

delete-user-data/README.md

@@ -8,25 +8,25 @@
 
 **CONFIGURATION PARAMETERS:**
 
-* Deployment location: *Where should the extension be deployed? You usually want a location close to your database. For help selecting a location, refer to the [location selection guide](https://firebase.google.com/docs/functions/locations#selecting_regions_for_firestore_and_storage).*
+* Deployment location: Where should the extension be deployed? You usually want a location close to your database. For help selecting a location, refer to the [location selection guide](https://firebase.google.com/docs/functions/locations#selecting_regions_for_firestore_and_storage).
 
-* Cloud Firestore paths: *Which paths in your Cloud Firestore instance contain user data? Leave empty if you don't use Cloud Firestore.
+* Cloud Firestore paths: Which paths in your Cloud Firestore instance contain user data? Leave empty if you don't use Cloud Firestore.
 Enter the full paths, separated by commas. You can represent the User ID of the deleted user with `{UID}`.
-For example, if you have the collections `users` and `admins`, and each collection has documents with User ID as document IDs, then you can enter `users/{UID},admins/{UID}`.*
+For example, if you have the collections `users` and `admins`, and each collection has documents with User ID as document IDs, then you can enter `users/{UID},admins/{UID}`.
 
-* Realtime Database paths: *Which paths in your Realtime Database instance contain user data? Leave empty if you don't use Realtime Database.
+* Realtime Database paths: Which paths in your Realtime Database instance contain user data? Leave empty if you don't use Realtime Database.
 Enter the full paths, separated by commas. You can represent the User ID of the deleted user with `{UID}`.
-For example: `users/{UID},admins/{UID}`.*
+For example: `users/{UID},admins/{UID}`.
 
-* Cloud Storage paths: *Where in Google Cloud Storage do you store user data? Leave empty if you don't use Cloud Storage.
+* Cloud Storage paths: Where in Google Cloud Storage do you store user data? Leave empty if you don't use Cloud Storage.
 Enter the full paths, separated by commas. You can represent the User ID of the deleted user with `{UID}`. You can use `{DEFAULT}` to represent your default bucket.
-For example, if you are using your default bucket, and the bucket has files with the naming scheme `{UID}-pic.png`, then you can enter `{DEFAULT}/{UID}-pic.png`. If you also have files in another bucket called `my-awesome-app-logs`, and that bucket has files with the naming scheme `{UID}-logs.txt`, then you can enter `{DEFAULT}/{UID}-pic.png,my-awesome-app-logs/{UID}-logs.txt`.*
+For example, if you are using your default bucket, and the bucket has files with the naming scheme `{UID}-pic.png`, then you can enter `{DEFAULT}/{UID}-pic.png`. If you also have files in another bucket called `my-awesome-app-logs`, and that bucket has files with the naming scheme `{UID}-logs.txt`, then you can enter `{DEFAULT}/{UID}-pic.png,my-awesome-app-logs/{UID}-logs.txt`.
 
 
 
-**NON-CLOUD FUNCTION RESOURCES CREATED**:
+**CLOUD FUNCTIONS CREATED:**
 
-* clearData (firebaseextensions.v1beta.function)
+* clearData (providers/firebase.auth/eventTypes/user.delete)
 
 
 
@@ -38,13 +38,13 @@ You can configure this extension to delete user data from any or all of the foll
 
 This extension is useful in respecting user privacy and fulfilling compliance requirements. However, using this extension does not guarantee compliance with government and industry regulations.
 
-### Additional setup
+#### Additional setup
 
 Depending on where you'd like to delete user data from, make sure that you've set up [Cloud Firestore](https://firebase.google.com/docs/firestore), [Realtime Database](https://firebase.google.com/docs/database), or [Cloud Storage](https://firebase.google.com/docs/storage) in your Firebase project before installing this extension.
 
 Also, make sure that you've set up [Firebase Authentication](https://firebase.google.com/docs/auth) to manage your users.
 
-### Billing
+#### Billing
 
 This extension uses other Firebase or Google Cloud Platform services which may have associated charges:
 

delete-user-data/extension.yaml

@@ -90,8 +90,6 @@ params:
     label: Cloud Firestore paths
     example: users/{UID},admins/{UID}
     required: false
-    validationRegex: '^[^/]+(/[^/]+)*$'
-    validationErrorMessage: Must be a valid Cloud Firestore path.
     description: >-
       Which paths in your Cloud Firestore instance contain user data? Leave empty if
       you don't use Cloud Firestore.
@@ -106,8 +104,6 @@ params:
     label: Realtime Database paths
     example: users/{UID},admins/{UID}
     required: false
-    validationRegex: '^[^\s.#$[\]]+$'
-    validationErrorMessage: Database path(s) contains spaces and/or invalid characters.
     description: >-
       Which paths in your Realtime Database instance contain user data? Leave empty if you
       don't use Realtime Database.
@@ -121,8 +117,6 @@ params:
     label: Cloud Storage paths
     example: "{DEFAULT}/{UID}-pic.png,my-awesome-app-logs/{UID}-logs.txt"
     required: false
-    validationRegex: '^\S+$'
-    validationErrorMessage: Invalid Storage path.
     description: >-
       Where in Google Cloud Storage do you store user data? Leave empty if you
       don't use Cloud Storage.

exts-test-data/README.md

@@ -1,9 +1,8 @@
-# Mods Test Data
+# Extensions Test Data
 
-This package will populate some test data for the following mods:
+This package will populate some test data for the following extensions:
 
-- firestore-recursive-delete
-- user-data-deletion
+- delete-user-data
 
 To run the package, you'll need:
 

exts-test-data/index.ts

@@ -82,22 +82,12 @@ const uploadFile = async (
   console.log(`Uploaded file to path: '${bucketPath}/${destinationPath}'`);
 };
 
-const populateFirestoreRecursiveDeleteData = async (): Promise<void> => {
-  console.log("---------------------------------------------------------");
-  console.log("Populating data for firestore-recursive-delete");
-  console.log("---------------------------------------------------------");
-  await createFirestoreDocument("nested/doc");
-  await createFirestoreDocument("nested/doc/path/doc");
-  console.log("Created nested collection in Firestore under path: '/nested'");
-  console.log();
-};
-
 const populateUserDataDeletionData = async (
   projectId: string
 ): Promise<void> => {
   // delete-user-data
   console.log("---------------------------------------------------------");
-  console.log("Populating data for firestore-recursive-delete");
+  console.log("Populating data for delete-user-data");
   console.log("---------------------------------------------------------");
   // 1) Create some users
   await createUser("1", "User 1");
@@ -129,20 +119,19 @@ const run = async (): Promise<void> => {
     databaseURL: `https://${projectId}.firebaseio.com`,
   });
 
-  await populateFirestoreRecursiveDeleteData();
   await populateUserDataDeletionData(projectId);
 };
 
 run()
   .then(() => {
     console.log("---------------------------------------------------------");
-    console.log("Finished creating mods test data");
+    console.log("Finished creating extensions test data");
     console.log("---------------------------------------------------------");
     process.exit();
   })
   .catch((error) => {
     console.log("---------------------------------------------------------");
-    console.error("Error creating mods test data:");
+    console.error("Error creating extensions test data:");
     console.error(error);
     console.log("---------------------------------------------------------");
     process.exit();