kbrew-dev / kbrew

kbrew is homebrew for Kubernetes
Apache License 2.0
191 stars 19 forks source link

Add a subcommand to print complete recipe for an app #120

Open PrasadG193 opened 3 years ago

PrasadG193 commented 3 years ago

The command could be like - kbrew recipe kafka which should print complete recipe details for better understanding or debugging

sahil-lakhwani commented 3 years ago

I think we can use the info command by having a sub-command or a flag (--verbose). Thoughts?

JOSHUAJEBARAJ commented 3 years ago

I would llike to work on this issue, Let me know how we can take forward this issue

sahil-lakhwani commented 3 years ago

hey @JOSHUAJEBARAJ :wave: You might want to look at the implementation of the info command - it does a similar job of printing a summary of a recipe. This issue is for printing the complete recipe.

While we work to build a contributing guide, you can use the Makefile to build the binary from the source (make build) after you make any changes Let us know if you need any help!

JOSHUAJEBARAJ commented 3 years ago

Hey Sahil 👋 I had look at the info Command Can You explain what is the additional information you want to print

For example the kbrew info argo-cd gives the below output

repository:
  name: argo
  url: https://argoproj.github.io/argo-helm
  type: helm
version: 3.6.2

THe registry config looks like something like this for the argo-cd

apiVersion: v1
kind: kbrew
app:
  repository:
    name: argo
    url: https://argoproj.github.io/argo-helm
    type: helm
  namespace: "argocd"
  sha256:
  version: 3.6.2

What are the additional detail it should Print ?

sahil-lakhwani commented 3 years ago

Taking an example the longhorn recipe, kbrew info prints only the metadata which has pre/post install apps. With a new command/sub-command we would like to print the entire recipe, which also includes steps, args, etc. So basically the recipe as it is in the file. We can do it as a new command to kbrew or a new subcommand to info - kbrew info all for example

deepankur797 commented 2 years ago

@JOSHUAJEBARAJ are you still working on this issue ? If not, may I take this forward and start working on it.

JOSHUAJEBARAJ commented 2 years ago

@deepankur797 Sure You can go ahead and work on this issue