Show BCD mapping progress on front page

[jcscottiii]

This is a temporary feature. The plan is to manually update the score in the storage bucket and have the frontend query that.

App deployers will have to update the score manually. This should only last through December.

The BCD mapping progress will be hosted in a publicly exposed GCS bucket. The changes modify the frontend configuration so that the URL for json is passed in. We add a new WEB_FEATURES_PROGRESS_URL environment variable. This is where app deployers can configure the setting. (Just like the other frontend settings)

The data will have the following form: {"bcd_map_progress": number}

Users will see this percentage on the overview page. When the mapping is complete, we can turn off the feature by setting the body to {"is_disabled": true} in the GCS bucket.

Architecture of changes:

webstatus-overview-content

This is the visual component that we added the percentage to. This is responsible for the presentation layer for this change via a new renderMappingPercentage.

webstatus-webfeature-progress-service

This is a new service that maintains the business logic to get the data from the GCS bucket. It communicates to consumers via a new context webFeatureProgressContext. While webstatus-overview-content is the only consumer, we could easily support other visual components by having them consume the data from the context. And each of those visual components can have their own presentation.

Other changes:

• Automatically populate the local GCS emulator with a bucket called webfeatures on startup. The bucket has a file called progress.json like staging and prod.
• Modify Makefile to forward the ports to the GCS emulator.
• Make GCS emulator a pre-requisite for the frontend to come up by modifying frontend/skaffold.yaml
• Adding instructions that the app deployer will need to follow to update the value

[jrobbins]

What's the timeframe on the how long we will need to display this number? Was it estimated to be just from now until the end of the year or early 2025, or will it always be needed? Why mark it as disabled rather than remove the code?

[jcscottiii]

The idea is to remove the code but we can easily turn this feature off while we wait for the next engineer to do the deployment (or if we need to turn it off beforehand for any other reasons)

Timeframe: this ideally would go away by mid December.

[jrobbins]

but we can easily turn this feature off while we wait for the next engineer to do the deployment (or if we need to turn it off beforehand for any other reasons)

What's the procedure to disable showing this text?

[jrobbins]

LGTM, but I had one clarification question in a reply to an earlier comment.

[jcscottiii]

but we can easily turn this feature off while we wait for the next engineer to do the deployment (or if we need to turn it off beforehand for any other reasons)

What's the procedure to disable showing this text?

Good question. I have added instructions to the DEPLOYMENT.md on how to handle this