Skip to content

Add subplat-cirrus to repositories.yaml #963

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+21 −0
Open

Add subplat-cirrus to repositories.yaml #963

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6c67887
Add subplat-cirrus to repositories.yaml
relud Nov 6, 2025
854e32c
Update repositories.yaml
relud Nov 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions repositories.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2121,3 +2121,24 @@ applications:
moz_pipeline_metadata_defaults:
expiration_policy:
delete_after_days: 760

- app_name: subplat_cirrus
Copy link
Contributor

@sean-rose sean-rose Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question (non-blocking): Based on the dependencies including glean-server, is this perhaps intended to be specific to the SubPlat backend? Or would it also be used for the SubPlat frontend?

If it is specific to the SubPlat backend, then I think it'd be good to change the app_name, v1_name, and app_id to be more similar to the values for the existing subscription_platform_backend app (plus the appropriate Cirrus-specific suffix).

Copy link
Contributor Author

@relud relud Nov 7, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tl;dr this isn't backend specific

More precisely, while we expect only the backend to use it, we expect any experiments in the frontend to receive feature configuration from the backend, not directly from cirrus. This matches with accounts_cirrus which is also only used in the backend.

integrating with cirrus on the frontend would be for applications that don't have a suitable backend, e.g. static sites that only have client-side code.

canonical_app_name: "Subscription Platform (Cirrus)"
app_description: |
Mozilla Subscription Platform is Mozilla's subscription management
solution for account-based end-user services and features.
url: https://github.com/mozilla/fxa
notification_emails:
- [email protected]
branch: main
metrics_files: []
ping_files: []
dependencies:
- glean-server
- nimbus-cirrus
channels:
- v1_name: subplat-cirrus
app_id: subplat.cirrus
moz_pipeline_metadata_defaults:
expiration_policy:
delete_after_days: 760