Allow KubernetesMockServer in TestConfiguration be created without https

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, kubernetes
Domain
testing

Research direction

Start by reading TestConfiguration and TestConfigurationProperties to trace how KubernetesMockServer settings are created and passed through. Make the HTTPS choice configurable through TestConfigurationProperties, then verify that a non-secure KubernetesMockServer can be started through the test configuration.

Written by the indexing model from the issue text.

Description

I had some problems with my test related to security and because of that I wanted to ue the KubernetesMockServer started in non secure mode. Unfortunatelly this is not configurable in the TestConfiguration class.
What I want to propose is to make this configurable through the class TestConfigurationProperties.

I can offer a PR if you consider this acceptable

Dominant language
Java
Stars
58
Forks
31
Avg merge
2d 3h
Merged PRs (30d)
8

Getting set up

  • No Dockerfile or Docker Compose file
  • No pull request template
  • Read 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.

More from operator-framework/josdk-spring-boot-starter

All issues in operator-framework/josdk-spring-boot-starter

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.