spinframework / spinframework/spin-operator

e2e test for ensuring relevant resources are deleted when spinapp is deleted

Open
#157 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
289
Forks
34
PR merge metrics
No merged PRs in 30d

Description

Includes deployment, service, runtimeconfig secret. Inspired by @calebschoepp's comment here

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no file or test entry point. Review the discussion linked from pull request #156 and locate the existing end-to-end test structure; done means an end-to-end test confirms the deployment, service, and runtimeconfig secret are deleted when the SpinApp is deleted.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.