miki3421 opened a new pull request, #13: URL: https://github.com/apache/openserverless-testing/pull/13
This draft adds the missing `0.9.0` SSO smoke script and mock OIDC provider from `0.9.1` (`e017ff5fb5b1147cdb772aa584223d6e0d6c83da`), including the upstream transient-login retry handling. Only the deployment names are adapted: namespace `openserverless`, StatefulSet `openserverless-system-api`, and `ops setup openserverless hello`. The established `tests/all.sh` and deployment scripts remain unchanged. Run the new test explicitly with `bash tests/11-sso-mock.sh kind` on a disposable cluster with the companion task/admin-api backports installed. ### Validation - Shell syntax and Python compilation passed. - Four local HTTP integration scenarios passed between this mock provider and the companion admin-api: valid confidential login, wrong user password, wrong client secret and missing required group. Token signatures were verified by the real OIDC validator; CouchDB and Kubernetes were mocked. - Source comparison confirmed the scripts retain their `0.9.1` behavior apart from deployment names. - `git diff --check` passed. ### Existing issue reported without changing the established suite `tests/all.sh` can record a failed test and still exit with status 0. Reproduced with isolated stub scripts: `6-login.sh` exited 7, `_results` recorded `FAIL ./6-login.sh`, and the runner exited 0. The new SSO script is opt-in and propagates its own failures when invoked directly; the runner's existing behavior is outside this backport. No cluster resources were created and no live deployment/provisioning test was run. The full smoke test remains necessary once the companion task and admin-api changes have been built and deployed. Companion drafts: https://github.com/apache/openserverless-admin-api/pull/52 and https://github.com/apache/openserverless-task/pull/229 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
