When viewing a build that reconfigures pipelines, it's hard to tell which pipelines were actually changed:

Quick suggestion: highlight it in yellow, like the get step? Or the opposite - dim steps which had no changes to apply? No strong preference!

This would likely involve emittin

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

If an invalid token for a local user exists in argocd-secret, the API will refuse to process any request with an error message similar to:

FATA[0002] rpc error: code =

Summary

jx create addon istio doesn't work
since v 1.5 istio moved to operator so no folder install/kubernetes/helm/istio

Steps to reproduce the behavior

jx create addon istio

Output

Istio package already downloaded: /Users/msirs/.jx/cache/istio-1.6.0-osx.tar.gz
error: Could not find folder install/kubernetes/helm/istio inside istio clone at /Users/msirs/.jx/cache/istio

Sorta bad titlte, but I'd love to get a list of all toggles that are responding with 100% yes and are unchanged for the last 30 days. In that case, you can probably delete the toggle as it's not necesarry any more.

In the same vein, also exposing all toggles that has no metrics for the last 30 days would be great for the same use case.

Opening here instead of in unleash-frontend as I want to

While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:

$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR  ResourceNotFoundException: The specified log group does not exist.
	status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264

This error does not occur with the `-f

I was thinking that we could extract the eslint config file into his own module so that we can easily reuse this across any OC related repo in the form of eslint extends.

This because we now have the @opencomponents organization and quite few repos, and i

What happened:

UI is loading all the step log data in memory and looping through the data to create a blob to make it downloadable. This does not work for large step log files where there are hundred thousands of log lines.

What you expected to happen:

1. UI should not do any custom logic and should defer to API for log download.
2. New API to download step logs with proper cachi

What is the problem?
When visiting a page whose availability is determined from the server state, there is a time lag before the response is shown to the user.

Your solution
We can show an intermediate loading page to let users know that we have received the request and the server is validating the page access request.

Alternatives considered
Currently, an empty page is shown.