chore: add admin campaign applications

[gparlakov]

• add a login fixture
• add a test that verifies the current admin list of campaign applications

Motivation and context

Authentication of a user in e2e tests context
Verification of Admin Campaign Application pages

Testing

run the e2e tests

Environment

New environment variables:

• PODKREPI_EMAIL: email for user auth
• PODKREPI_PASSWORD: password for user auth

[github-actions]

✅ Tests will run for this PR. Once they succeed it can be merged.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[sashko9807]

E2E job seems to fail.
Though im not sure if any auth-based e2e test would ever pass, as we don't have a job to setup keycloak, which is needed for auth(or at least I don't see one).

[gparlakov]

Let me see if I can add a step for that keycloak

…

On Mon, Jul 15, 2024, 11:14 PM Aleksandar Petkov ***@***.***> wrote: E2E job seems to fail. Though im not sure if any auth-based e2e test would ever pass, as we don't have a job to setup keycloak, which is needed for auth(or at least I don't see one). — Reply to this email directly, view it on GitHub <#1882 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA2SEVZMEYKFRLKEH6XIBY3ZMQUTHAVCNFSM6AAAAABKVEKFECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRZGMZDANBYGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[gparlakov]

E2E job seems to fail.

I can't seem to find the run of those (neither unit-tests.yaml or playwright.yaml-s workflow logs show a failed run) @sashko9807 was that run locally or via the actions?

[gparlakov]

@sashko9807 sorry - it looks like the latest playwright.yaml (addition of keycloak) was ignored - is this a cache thing? Or did I miss something?

Notice the command (on the left) was docker-compose up -d pg-db while the update (on the right) includes the keycloak service as well...

[sashko9807]

@sashko9807 sorry - it looks like the latest playwright.yaml (addition of keycloak) was ignored - is this a cache thing? Or did I miss something?

Notice the command (on the left) was docker-compose up -d pg-db while the update (on the right) includes the keycloak service as well...

Probably the keycloak step should be added and merged from a separate commit first.

Though I am not sure whether it would work, because the API container still requires a secret to connect with keycloak. Will have to check whether we can preconfigure it from docker compose first.