We recently upgraded to ArgoCD v2.1.0+d0b2d55 and have noticed that when browsing the UI the history in Firefox gets really polluted when changing pages.

Steps to reproduce;

1. Open a new browser tab
2. Navigate to ArgoCD
3. Long-press back button on browser

Expected

• A single entry for ArgoCD

Actual

History contains 15 separate entries for the same URI, preventing the

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.

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

Problem

Installation is not straightforward enough for some users.

Suggestion

Use goreleaser (with a homebrew option for mac users, etc). The resulting installation section of your readme could then look something like [this](https://github.com/scottrigby/example-dep-no-vendor/#example-installati

Describe the bug

There is a bug in podinfo chart which will not deploy service if you enabled canary, even though you enabled service via helm values.

https://github.com/fluxcd/flagger/blob/main/charts/podinfo/templates/service.yaml#L1

To Reproduce

If you set values like this, it will not deploy service.

service:
  enabled: true # service will not be deployed if ca

Using #1671 as an example we could add unit tests for the flux create secret git/helm/tls --export commands and validate the YAML output against golden file.

Summary

Validate Helm Repos as the user adds them.

Motivation

Adding an invalid repo will stop chart deployment as argocd validates all the helm repos before deploying any helm chart.

Proposal

If repo url is : https://helm.devtron.ai/

https://helm.devtron.ai/index.yaml should return a 200 http status

Summary

The output of the status command is different if we run status with the --watch flag set to true or false. I am not sure if it was designed in that way, but for me, it is a bit confusing. Let's compare:

kubectl-argo-rollouts status example-spring-boot-prod-01 --namespace test-argo-prod --watch=true
Paused - BlueGreenPause
kubectl-argo-rollouts status example-spring-boot-prod

Expected behavior

render runs function and generates resources.

Actual behavior

render seems to exit early if a package only contains the functionConfig and Kptfile.
Quick trace led me to https://github.com/GoogleContainerTools/kpt/blob/57b52103576b7a195502dc10a4ad608570095e47/internal/cmdrender/executor.go#L339-L342

eval works as expected.

Information

Authentication via Azure/aad-pod-identity for keyvault access could be a good feature to avoid use of clientId/ clientSecret in chart values. Don't you think ?

Expected behavior

When running the terraform step, all plan contents should be visible or there should be a scroll bar.

Actual behavior

A scrollbar never appears, and content clips off the bottom of the screen. If the page zoom is changed, content reflows and a scroll bar appears.

Information

• Ship version: 0.43.1
• Command line run: ship init ./ship.yaml
• Chrome v

valuesFromFile:
  chartFileRef:
    myScript: path/to/file.js
  externalSourceRef:
    defaultScript: https://raw.githubusercontent.com/cdenneen/example/master/script.js

result in equivalent of:

helm install --set-file key=path/to/file.js

myScript: |
  const { events, Job } = require("brigadier")
  function run(e, project) {
    console.log("this i

Long tags with all digits seem to be changed to scientific notation at some point.

As a: developer

I want: the dashboard to display ring names I've configured in bedrock.yaml

So that: I can see the right ring name for services in the dashboard

Describe the solution you'd like:
Following the work on microsoft/bedrock#1313, any branch can be associated with any ring name. Currently, the introspection script assumes that the branc

As discussed in slack.

In comparison to skaffold (another deployment tool), kapp only reports if the condition was met or not. I'd like to see more information about the stabilization process e.g:

Waiting for deployments to stabilize...
 - production:deployment/demo: creating container service
    - production:pod/demo-5cf5f768d4-x9xfr: creating container service
 - production:deploy

What would you like to be added:

https://github.com/pipe-cd/pipe/blob/2fda7c82def6c81aff29ab08d1283851f5f49f06/pkg/app/piped/cloudprovider/ecs/task.go#L45-L54

Why is this needed:

Currently, SchemaHero assumes that every Postgres table will be deployed to the public schema. It should be possible to specify the schema when defining a table