Checklist:

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

Describe the bug

Values from an Application CRD values block that overrides values from value files are not visualized under the App Details -> Parameters -> Parameters section.

**To Repro

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

In lieu of #283, implement Stackdriver Canary Analysis for use in GKE.

The TOC on the right hand side of https://toolkit.fluxcd.io/guides/helm-operator-migration/ is very crowded, let's add a mini-TOC at the top of the document to provide links to:

• discussion of breaking changes
• api spec changes
• migration strategy
• FAQ

Can you add autocomplete to a command in bash? Pressing the tab key displays subcommands

Expected behavior

Formatting configs would not break yaml docs that includes anchors and references.

Actual behavior

Running the kpt fn render command on a configuration that includes anchors and references ends up putting the anchors before the references in the yaml, thereby making the yaml invalid.

Information

Steps to reproduce the behavior

kpt pkg get https:

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