Repackage spring-cloud-kubernetes-configserver so that it can also be used as a dependency
envgap__spring-cloud__spring-cloud-kubernetes-1456
01 / FAILURE SIGNATURE
As reported upstream
No identifying execution failure has been captured.
Not a benchmark task.
- The project already builds and runs before the fix, so there is nothing to repair.
02 / ENVIRONMENT RECIPE
- Base commit
68438886f3e4abd948b0d9f58f603cb51a81fb36- Manifest
spring-cloud-kubernetes-controllers/pom.xml- Reproduce
Awaiting issue-specific recipe- Run under trace
Awaiting a meaningful runtime command
03 / ORIGINAL ISSUE TEXT
spring-cloud/spring-cloud-kubernetes #1456 · read the original issue
I am trying to add security to the spring-cloud-kubernetes-configserver, and the only way I see is to fork the project and add the necessary changes like dependencies and configuration. It would be great if the spring-cloud-kubernetes-configserver was packaged in a way that it can be either directly launched as a service (the way it is today) or that it can also be used as a dependency for a custom built config server with enhanced functionality (similar to the spring-cloud-config-server on which it is based). There seems to be a simple solution that only involves changing the classifier in the repackage goal of the build script that would allow both usages, as described here: https://stackoverflow.com/questions/40089443
04 / LABELS
Labels from the report text only; not yet run
No supported category has been assigned.
Label rules and the text that matched
[]