kubernetes-sigs/cluster-api

Implement a smoke test for clusterctl plugins

Open

#10,219 opened on Feb 29, 2024

View on GitHub
 (5 comments) (0 reactions) (1 assignee)Go (1,532 forks)auto 404
area/clusterctlhelp wantedkind/featurepriority/important-longtermtriage/accepted

Repository metrics

Stars
 (4,267 stars)
PR merge metrics
 (PR metrics pending)

Description

What would you like to be added (User Story)?

As a developer I would like to change clusterctl with confidence As a user I would like to have guarantee about clusterctl plugins

Detailed Description

We should implement a smoke test about clusterctl plugin, creating a foo plugin a checking that it is loaded and executed when running clusterctl foo

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature /area clusterctl /triage accepted

/help

Contributor guide

Research direction
Investigate how clusterctl discovers and executes plugins. Review existing plugin examples in the codebase. Create a simple plugin (e.g., 'foo') and write a test that verifies it is loaded and runs when calling 'clusterctl foo'. Ensure the test is isolated and can be run as part of CI.
Tech stack
go
Domain
clibackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70