Check for differences between `main` & production about cwa-server HOT 15 CLOSED

@hilmarf is on a longer absent, so it will take a little longer until he can get back to this (talking approx. 4 weeks). I will see if I can do something meanwhile.

from cwa-server.

Is it reasonable to assume that the data on the production system is always in alignment to main/resources/application.yaml?

That would be my understanding reading main/docs/DISTRIBUTION.md including

• https://github.com/corona-warn-app/cwa-server/blob/main/docs/DISTRIBUTION.md#configuration
• https://github.com/corona-warn-app/cwa-server/blob/main/docs/DISTRIBUTION.md#configuration-properties

from cwa-server.

Hi @Ein-Tim,
Hi @MikeMcC399,

to answer your question: "Is it reasonable to assume that the data on the production system is always in alignment to main/resources/application.yaml?"
I would clearly say: "No!"

Reason: the application.yaml contains a bunch of environment variables, which we can't always keep in sync or even don't want to publish - think of DB passwords, private keys and certificates - such sensitive information is stored in a Vault instance, which is connected to the runtime environment at OTC.

Nevertheless, we're sorry for the confusion (#1962). When we first made the change to minimum Android version requirements, we were facing a large discussion why we're excluding so many devices and had to very quickly revert those settings. Unfortunately the quickest way was to overwrite the environment variables via Vault, which we never played back into the sources. #1965 does this now.

🖖 live long and prosper
Hilmar

from cwa-server.

@hilmarf

Thanks for the clarification & for fixing the issue @MikeMcC399 reported.
Please, could you still make sure that the data that is published here on GitHub is in sync with the data on the PROD server?

Thank you!

from cwa-server.

@Ein-Tim - we'll check it once we're done with #1949 which needs currently our max attention.

Thanks for your patience.

from cwa-server.

All,
as you already might have realized, we are moving directly into direction of maintenance and ramp-down of the CWA.
This also implies that there will be no new major requirements from the customer, especially on the backend side. Thank you all for keeping an eye on our respositories being in sync; we are of course aware of that.
However, looking at current resources and timeline, we will most likely push these house-keeping activities into the last phase of CWA before the GitHub project is either closed or transferred/handed over.
We currently see neither the need nor the ability to put effort into this synchronization in the short term.
Thanks for your understanding.

from cwa-server.

@GisoSchroederSAP

Okay, thank you very much for the information! I'll leave this issue open until the task has been performed (or one of the maintainers close it).

from cwa-server.

Hi @Ein-Tim, as you may have noticed. The mobile app states: "Es wird nur noch bis zum 30. April 2023 möglich sein, andere Personen ... zu warnen!"
That's why we'll turn the backend off as there is no reason to keep servers running #sustainability_responsibility.

Nevertheless, here are three excerpts from the public (this) repository, the private admin repository (used for the helm-charts and deployments) and the secrets storage (vault, which has highest priority in case variables are defined).
I've only quickly scanned through it and not found any differences to the public defaults... but maybe someone else has time and capacity to double check.

I hope this is satisfying and wish everyone a nice long weekend!
🖖 live long and prosper
Hilmar

from cwa-server.

@hilmarf

For sure, I absolutely understand this! Thank you for your work!

Have a nice evening!

from cwa-server.

@hilmarf

we'll check it once we're done with #1949 which needs currently our max attention.

• #1949 is now merged

from cwa-server.

Is someone working on this issue? I'll not close it, as I consider it as transparency relevant that the production server and the main branch of this repository are in sync.

from cwa-server.

only 9 days left... closing this, due to lack of remaining resources

from cwa-server.

@hilmarf

According to the CWA website "CWA development ends on May 31, 2023". Isn't this a good task you could perform after the infrastructure shuts down on 01.05.2023, or are there also no resources for this, in my eyes very important and transparency relevant, in May?

from cwa-server.

See also https://www.coronawarn.app/en/faq/results/#ramp_down_github, which says:
"Until May 31, 2023, the source code will be maintained as part of CWA development."

from cwa-server.

@hilmarf

Thank you for the answer Hilmar, sounds good to me!

Have a nice long weekend!

from cwa-server.