Support for a pre-packaged chart in frigate #26
Comments
|
I have written something that can deal with this scenario and I am putting it up for review soon and will refactor it as we all discuss in this forum. |
raul1991
pushed a commit
to raul1991/frigate
that referenced
this issue
Nov 10, 2020
If a user packs the chart properly (including its dependent charts) so he would only like frigate to just go through them and just dump the values from them that way it already does. The only thing would be to NOT run the repo update and the dep update commands. One thing to note here is that the above commands only slow down the whole recursion drastically (I had to wait for 20 mins). With this improvement a flag called --no-update has been introduced which would not invoke the the aforementioned commands during the traversal. Fixes rapidsai#26
raul1991
pushed a commit
to raul1991/frigate
that referenced
this issue
Nov 10, 2020
If a user packs the chart properly (including its dependent charts) so he would only like frigate to just go through them and just dump the values from them that way it already does. The only thing would be to NOT run the repo update and the dep update commands. One thing to note here is that the above commands only slow down the whole recursion drastically (I had to wait for 20 mins). With this improvement a flag called --no-update has been introduced which would not invoke the the aforementioned commands during the traversal. Fixes rapidsai#26
raul1991
pushed a commit
to raul1991/frigate
that referenced
this issue
Nov 10, 2020
If a user packs the chart properly (including its dependent charts) so he would only like frigate to just go through them and just dump the values from them that way it already does. The only thing would be to NOT run the repo update and the dep update commands. One thing to note here is that the above commands only slow down the whole recursion drastically (I had to wait for 20 mins). With this improvement a flag called --no-update has been introduced which would not invoke the the aforementioned commands during the traversal. Fixes rapidsai#26
raul1991
pushed a commit
to raul1991/frigate
that referenced
this issue
Nov 10, 2020
If a user packs the chart properly (including its dependent charts) so he would only like frigate to just go through them and just dump the values from them that way it already does. The only thing would be to NOT run the repo update and the dep update commands. One thing to note here is that the above commands only slow down the whole recursion drastically (I had to wait for 20 mins). With this improvement a flag called --no-update has been introduced which would not invoke the the aforementioned commands during the traversal. Fixes rapidsai#26
raul1991
added a commit
to raul1991/frigate
that referenced
this issue
Nov 10, 2020
If a user packs the chart properly (including its dependent charts) so he would only like frigate to just go through them and just dump the values from them that way it already does. The only thing would be to NOT run the repo update and the dep update commands. One thing to note here is that the above commands only slow down the whole recursion drastically (I had to wait for 20 mins). With this improvement a flag called --no-update has been introduced which would not invoke the the aforementioned commands during the traversal. Fixes rapidsai#26
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my case , I usually update my chart ie pack it properly (including its dependent charts) so I would like frigate to just go through them and just dump the values from them that way it already does. The only thing would be to NOT run the
repo update and the dep updatecommands.One thing to note here is that the above commands only slow down the whole recursion drastically (I had to wait for 20 mins). With this improvement I also would like to propose a flag called
--no-updatewhich would not invoke the the aforementioned commands during the traversal.The text was updated successfully, but these errors were encountered: