hasura / hasura/gitkube

Improve e2e test

Open
#28 1 comment 0 reactions 0 assignees View on GitHub
good first issue
Dominant language
Go
Stars
3.8k
Forks
197
PR merge metrics
No merged PRs in 30d

Description

Currently, the e2e test fails when the following two resources already exist:
```
Error from server (AlreadyExists): error when creating "STDIN": customresourcedefinitions.apiextensions.k8s.io "remotes.gitkube.sh" already exists
Error from server (AlreadyExists): error when creating "STDIN": clusterrolebindings.rbac.authorization.k8s.io "gitkube" already exists
```
For the CRD, we just need to ignore the error and for clusterrolebindings we can just use the test namespace name.

Contributor guide

Open the contributing guide

Research direction

Start by locating the e2e test setup that creates the Kubernetes CRD and clusterrolebinding. Reproduce the failure with those resources already present, then verify the test handles the existing CRD and uses the test namespace in the binding name. Done means the e2e test passes in both clean and pre-existing-resource environments.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.