Roland Huß
Roland Huß
Curently we are using a struct `KnParams` as the _context_ that we pass down into specific commands so that they can access the various services: ```golang type KnParams struct {...
At the moment we have some inconsistencies when it comes to messages. There are also no written rules how messages should look like. Examples: ``` Service 'k8s-event-display' successfully created in...
Also bumped up snapshot version to 4.1-SNAPSHOT
Think about an enricher which adds a Component CRD for the project at hand. @cmoulliard do you have a link to the Component CRD specs and discussions?
Documentation is incomplete and outdated Documentation should be close to the generated standard Maven Plugin Documentation format. This work should be tackled for the new rebranded fmp.
[fabric8-kit](https://github.com/fabric8io/fabric8-kit) is meant to encapsulate the main abstraction developed for this plugin. I.e. these are * Generators * Enrichers * Profiles Also the domain model, i.e. the Image configuration for...
Too many (random) properties ! Instead: Focus on native configuration format (i.e. fragments) for specific configurations Old similar issue #18 This should be performed for the new rebranded fmp.
Since all generated resource objects end up in the artifact jars within `META-INF/fabric8` they have to be independent of any concrete cluster installation (i.e. the must not contain the value...
Currently f-m-p uses some `@deprecated` methods from kubernetes-client which should be removed.
### Description The current way how the API client is created and how the decision is made whether an OpenShift or Kubernetes client should be used in burried mostly in...