Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix integration tests for OIDC in Charmed Kubeflow 1.7+ #174

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

ca-scribner
Copy link
Contributor

refactors the integration test CI to:

  • use the latest/edge version of oidc-gatekeeper
  • provide oidc-gatekeeper with the public-url config during setup rather than during web browsing. This is required because the oidc-gatekeeper v1.7+ will block the charm without this setting, and also because it makes more sense then changing oidc-gatekeeper settings in the fixture for a later test

Context: previously, the integration tests here incorrectly pinned OIDC to that from charmed kubeflow 1.4, which is not how we want our main branch testing to work.

refactors the integration test CI to:
* use the latest/edge version of oidc-gatekeeper
* provide oidc-gatekeeper with the public-url config during setup rather than during web browsing.  This is required because the oidc-gatekeeper v1.7+ will block the charm without this setting, and also because it makes more sense then changing oidc-gatekeeper settings in the fixture for a later test

Context: previously, the integration tests here incorrectly pinned OIDC to that from charmed kubeflow 1.4, which is not how we want our main branch testing to work.
@ca-scribner ca-scribner force-pushed the KF-5107-fix-integration-test-for-new-oidc branch from e52dea6 to 647ba93 Compare December 7, 2023 19:10
Copy link
Contributor

@orfeas-k orfeas-k left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's super weird that we ran integration tests with an old version of the charm for so long. Great catch on noticing that. Thank you @ca-scribner

@ca-scribner ca-scribner merged commit 6c7ad62 into main Dec 8, 2023
7 checks passed
@ca-scribner ca-scribner deleted the KF-5107-fix-integration-test-for-new-oidc branch December 8, 2023 14:45
ca-scribner added a commit that referenced this pull request Dec 8, 2023
refactors the integration test CI to:
* use the latest/edge version of oidc-gatekeeper
* provide oidc-gatekeeper with the public-url config during setup rather than during web browsing.  This is required because the oidc-gatekeeper v1.7+ will block the charm without this setting, and also because it makes more sense then changing oidc-gatekeeper settings in the fixture for a later test

Context: previously, the integration tests here incorrectly pinned OIDC to that from charmed kubeflow 1.4, which is not how we want our main branch testing to work.
ca-scribner added a commit that referenced this pull request Dec 8, 2023
refactors the integration test CI to:
* use the latest/edge version of oidc-gatekeeper
* provide oidc-gatekeeper with the public-url config during setup rather than during web browsing.  This is required because the oidc-gatekeeper v1.7+ will block the charm without this setting, and also because it makes more sense then changing oidc-gatekeeper settings in the fixture for a later test

Context: previously, the integration tests here incorrectly pinned OIDC to that from charmed kubeflow 1.4, which is not how we want our main branch testing to work.
kimwnasptd pushed a commit that referenced this pull request Dec 11, 2023
* fix integration tests for OIDC in Charmed Kubeflow 1.7+ (#174)

refactors the integration test CI to:
* use the latest/edge version of oidc-gatekeeper
* provide oidc-gatekeeper with the public-url config during setup rather than during web browsing.  This is required because the oidc-gatekeeper v1.7+ will block the charm without this setting, and also because it makes more sense then changing oidc-gatekeeper settings in the fixture for a later test

Context: previously, the integration tests here incorrectly pinned OIDC to that from charmed kubeflow 1.4, which is not how we want our main branch testing to work.

* pin CI to dependencies this branch was released to

Pins the charms used by integration tests as dependencies to their stable channel at time of release of this track, not to `latest/stable` which is expected to change over time.
kimwnasptd pushed a commit that referenced this pull request Dec 12, 2023
* fix integration tests for OIDC in Charmed Kubeflow 1.7+ (#174)

refactors the integration test CI to:
* use the latest/edge version of oidc-gatekeeper
* provide oidc-gatekeeper with the public-url config during setup rather than during web browsing.  This is required because the oidc-gatekeeper v1.7+ will block the charm without this setting, and also because it makes more sense then changing oidc-gatekeeper settings in the fixture for a later test

Context: previously, the integration tests here incorrectly pinned OIDC to that from charmed kubeflow 1.4, which is not how we want our main branch testing to work.

* pin CI to dependencies this branch was released to

Pins the charms used by integration tests as dependencies to their stable channel at time of release of this track, not to `latest/stable` which is expected to change over time.

* use rock for dex 2.31

uses rock built from https://github.com/canonical/dex-auth-rocks/blob/track/2.31.2/dex/rockcraft.yaml

---------

Co-authored-by: Orfeas Kourkakis <orfeas.kourkakis@canonical.com>
ca-scribner added a commit that referenced this pull request Jan 29, 2024
refactors the integration test CI to:
* use the latest/edge version of oidc-gatekeeper
* provide oidc-gatekeeper with the public-url config during setup rather than during web browsing.  This is required because the oidc-gatekeeper v1.7+ will block the charm without this setting, and also because it makes more sense then changing oidc-gatekeeper settings in the fixture for a later test

Context: previously, the integration tests here incorrectly pinned OIDC to that from charmed kubeflow 1.4, which is not how we want our main branch testing to work.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants