Simple renaming of operating mode

[ghachey]

Currently the Education Survey Tool can operate in either of the following mode:

• Production
• Development

There is a very minor issue with this. The Google Service Account keys used for the Development mode ends with _test (e.g. pacemis-education-survey-tool-test.json). To make this more clear I think the easiest is to simply rename the mode "Development" to "Testing" in the app. The other approach would be to create yet a whole new set of Google Service Accounts and rename it with _dev (e.g. pacemis-education-survey-tool-dev.json) but due to lots of files in those existing service accounts it might be more effort.

The related firebase remote configuration is currently "service_account_key_dev" which should be renamed "service_account_key_test". This way we end up with a clean naming convention:

• Firebase config: service_account_key_test
• Operating mode label: Testing
• Google Service Account Name and Key: "Pacific EMIS Education Survey Tool Test" and "pacemis-education-survey-tool-test.json"

The production remains the same with the following:

• Firebase config: service_account_key_prod
• Operating mode label: Production
• Google Service Account Name and Key: "Pacific EMIS Education Survey Tool Production" and "pacemis-education-survey-tool-prod.json"

And we now are also in the process of creating a third one called Training.

• Firebase config: service_account_key_train
• Operating mode label: Training (but not yet shown in the app)
• Google Service Account Name and Key: "Pacific EMIS Education Survey Tool Training" and "pacemis-education-survey-tool-train.json"

Of course, the exact same as above is true for all contexts (countries).

For the transition the current Firebase config: service_account_key_dev shall remain there containing the same key as the service_account_key_test so that older app versions continue operating as expected with the same Google Service Account.

A little pain with this easy work now I think will make it more clear for posterity and anybody else working on the project in the future.

[ghachey]

@maratomega OK, this seems mostly done. Some remaining cleanups include:

• Identify which tablet app mode (Production, Testing, Training) uses which firebase configuration key.
• Put the right encoded values in firebase configuration keys for those three modes.

But now is not the best time for it. Will leave this open until this final cleanup takes place.

[ghachey]

@maratomega Can I just get a confirmation from the developers that the firebase "prod_cert" key is no longer used in the new build provided? That it was completely replaced with "service_account_key_prod" (for the Production mode) and of course also

• service_account_key_dev (for the Testing mode)
• service_account_key_train (for the Training mode)

[maratomega]

@ghachey if it's not enough we can also share the sceensshots were in the code it used

[ghachey]

@ghachey if it's not enough we can also share the sceensshots were in the code it used

That is perfect.

[ghachey]

@maratomega I confirm that I have created all the context and photo folders for all the existing service accounts. A sample is shown below.

This means there is a CONTEXT and CONTEXT\photos folder in each of the prod, test and train accounts for each country deployment.

In addition to each country deployment there is also the default project Pacific EMIS (context is PACEMIS) which will eventually be used as demo, etc. and it too has the prod, test and train service accounts (and thus modes).

Does this make sense?

[ghachey]

@maratomega And your developers will find me annoying for this but I will request one final related little adjustment to be 100% consistent and clear. To follow the new terminology I would like them to edit the name of the firebase key shown below to "service_account_key_test". This will have to be done in each Firebase project.

This will of course then have to be edited at the relevant places in your code (like the one you showed me above).