E2E tests improvements #126
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…terraform, operator)
JillRegan
reviewed
Dec 15, 2025
JillRegan
approved these changes
Dec 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR applies the same way for running e2e tests as in 1Password Kubernetes operator and 1Password Terraform provider.
This will make the maintainers experience consistent across 1password repos.
Details about fork pr testing can be found the the
/docs/fork-pr-testing.md.This PR also introduces a way for the users to test the action locally using Service Account. Details can be found in
docs/local-testing.md.Note:
Local testing can be done only using Service Accounts, as
actfails when running e2e tests with Connect.When running act, the workflow writes
1password-credentials.jsoninside the Docker container, then runs docker compose. However, Docker Compose talks to the host's Docker daemon, which looks for the credentials file on the host filesystem — where it doesn't exist.TL;DR: File written in container → Docker mounts from host → file not found → Connect fails to start.
Workaround: Use Service Account tests locally (-j test-service-account). This will enable contributors quickly validate the changes using Service Account. Full e2e workflow using Connect will be testing in the GitHubCI.