-
Notifications
You must be signed in to change notification settings - Fork 85
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
[fcmv1] Manage FCM V1 Google Service Account Key in CLI #2197
[fcmv1] Manage FCM V1 Google Service Account Key in CLI #2197
Conversation
Size Change: +3.35 kB (0%) Total Size: 51.3 MB
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran this version of eas-cli
against your changes in www
and the UX looks good. Thank you! Requesting changes for deduping classes 🙏
edit: When you are ready with the amended changes, please re-request review!
packages/eas-cli/src/credentials/android/actions/AssignGoogleServiceAccountKeyForFcmV1.ts
Show resolved
Hide resolved
packages/eas-cli/src/credentials/android/actions/CreateGoogleServiceAccountKeyForFcmV1.ts
Outdated
Show resolved
Hide resolved
packages/eas-cli/src/credentials/android/actions/SetUpGoogleServiceAccountKeyForFcmV1.ts
Show resolved
Hide resolved
packages/eas-cli/src/credentials/android/utils/googleServiceAccountKey.ts
Show resolved
Hide resolved
Assigning actionsI agree with you here -- these actions makes sense to keep the submission and fcmv1 separate. eas-cli/packages/eas-cli/src/credentials/android/actions/AssignGoogleServiceAccountKey.ts Line 9 in eb9152a
Create GSAK actionsThere will be 3 'contexts' for creation:
IMO the most important bit of logging here is this fyi bit. For the generic case, we'd want the fyi to link a generic page which lists the pages for submissions and fcmv1. For the specialized FCM and Submission cases, we'd want the fyi to lead to their respective instructions for the permissions the user needs to assign to that GSAK. My vote is to refactor this one into a single class since there are 3 logging contexts, but the underlying logic is the same SetUp GSAK actionsI'm ok with what you have here 👍 |
eb9152a
to
813e46c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks reasonable to me 👍
Thanks for sharing the video from e2e testing the change and thanks for taking care of it 🙌
813e46c
to
b096105
Compare
# Why We need to amend these docs to support using a Google Service Account Key for sending Android notifications via FCM V1. These docs are linked in the CLI when users are configuring Google Service Account Keys for submissions and notifications. (See @quinlanj's comment on this PR in eas-cli: expo/eas-cli#2197 (comment)). # How 1. Update the top-level intro with an explanation of the two use cases for uploading a Google Service Account Key to EAS. 2. Move existing instructions for `eas submit` into a new subsection 3. Add a subsection for instructions for uploading GSAK for FCM V1 # Test Plan Get feedback on copy, check that preview markdown looks good
# Why We need to amend these docs to support using a Google Service Account Key for sending Android notifications via FCM V1. These docs are linked in the CLI when users are configuring Google Service Account Keys for submissions and notifications. (See @quinlanj's comment on this PR in eas-cli: expo/eas-cli#2197 (comment)). # How 1. Update the top-level intro with an explanation of the two use cases for uploading a Google Service Account Key to EAS. 2. Move existing instructions for `eas submit` into a new subsection 3. Add a subsection for instructions for uploading GSAK for FCM V1 # Test Plan Get feedback on copy, check that preview markdown looks good
b096105
to
44df163
Compare
@quinlanj I removed CreateGoogleServiceAccountKeyForFcmV1 and updated the logging in Let me know what you think. |
99510f4
to
91a1a29
Compare
/changelog-entry new-feature Support configuring a Google Service Account Key via |
ff02983
to
2090787
Compare
# Why NOTE: DO NOT LAND THIS UNTIL GRAPHQL CHANGES LAND IN WWW We're adding support for FCM V1 credentials, as Google is shutting down the FCM Legacy API for sending Android notifications in June. # How Add new prompts and refactor existing prompts to match this schematic: # Test Plan Verified all functionality e2e:
2090787
to
fc1461b
Compare
/changelog-entry new-feature Support configuring a Google Service Account Key via eas credentials, for sending Android Notifications via FCM V1 |
✅ Thank you for adding the changelog entry! |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2197 +/- ##
==========================================
- Coverage 54.16% 54.08% -0.08%
==========================================
Files 516 518 +2
Lines 18814 18894 +80
Branches 3969 3984 +15
==========================================
+ Hits 10188 10216 +28
- Misses 7934 7981 +47
- Partials 692 697 +5 ☔ View full report in Codecov by Sentry. |
# Why We need to amend these docs to support using a Google Service Account Key for sending Android notifications via FCM V1. These docs are linked in the CLI when users are configuring Google Service Account Keys for submissions and notifications. (See @quinlanj's comment on this PR in eas-cli: expo/eas-cli#2197 (comment)). # How 1. Update the top-level intro with an explanation of the two use cases for uploading a Google Service Account Key to EAS. 2. Move existing instructions for `eas submit` into a new subsection 3. Add a subsection for instructions for uploading GSAK for FCM V1 # Test Plan Get feedback on copy, check that preview markdown looks good
# Why We need to amend these docs to support using a Google Service Account Key for sending Android notifications via FCM V1. These docs are linked in the CLI when users are configuring Google Service Account Keys for submissions and notifications. (See @quinlanj's comment on this PR in eas-cli: expo/eas-cli#2197 (comment)). # How 1. Update the top-level intro with an explanation of the two use cases for uploading a Google Service Account Key to EAS. 2. Move existing instructions for `eas submit` into a new subsection 3. Add a subsection for instructions for uploading GSAK for FCM V1 # Test Plan Get feedback on copy, check that preview markdown looks good
# Why We need to amend these docs to support using a Google Service Account Key for sending Android notifications via FCM V1. These docs are linked in the CLI when users are configuring Google Service Account Keys for submissions and notifications. (See @quinlanj's comment on this PR in eas-cli: expo/eas-cli#2197 (comment)). # How 1. Update the top-level intro with an explanation of the two use cases for uploading a Google Service Account Key to EAS. 2. Move existing instructions for `eas submit` into a new subsection 3. Add a subsection for instructions for uploading GSAK for FCM V1 # Test Plan Get feedback on copy, check that preview markdown looks good
#146) * [1/1][docs] Add FCM V1 instructions to Google Service Account Key docs # Why We need to amend these docs to support using a Google Service Account Key for sending Android notifications via FCM V1. These docs are linked in the CLI when users are configuring Google Service Account Keys for submissions and notifications. (See @quinlanj's comment on this PR in eas-cli: expo/eas-cli#2197 (comment)). # How 1. Update the top-level intro with an explanation of the two use cases for uploading a Google Service Account Key to EAS. 2. Move existing instructions for `eas submit` into a new subsection 3. Add a subsection for instructions for uploading GSAK for FCM V1 # Test Plan Get feedback on copy, check that preview markdown looks good * Update creating-google-service-account.md Co-authored-by: Aman Mittal <[email protected]> --------- Co-authored-by: Aman Mittal <[email protected]>
Why
NOTE: DO NOT LAND THIS UNTIL GRAPHQL CHANGES LAND IN WWW
We're adding support for FCM V1 credentials, as Google is shutting down the FCM Legacy API for sending Android notifications in June.
How
Add new prompts and refactor existing prompts to match this schematic:
Test Plan
Verified all functionality e2e: