gitops

If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.

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.

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.

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

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

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

This is a follow-up to fluxcd/kustomize-controller#387 for aligning the behaviour implemented in the fix to that issue to all other controllers:

• image-automation-controller (ImageUpdateAutomation)
• image-reflector-controller (ImageRepository, ImagePolicy)
• source-controller (HelmRepository, HelmChart, GitRepository, Bucket)

Summary

Spawned from argoproj/argo-rollouts#1525.

If using workloadRef, the plugin set image command does not work. We made it work for undo but not for set image.

Diagnostics

What version of Argo Rollouts are you running? v1.1.0-rc1

**Message

We are adding support custom resource ordering in kpt live with the introduction of the depends-on annotation (GoogleContainerTools/kpt#2565). The resource references includes the namespace and name of resources, which means we should make sure they are updated when using the set-namespace and ensure-name-substring functions are used. We should update the functions to

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.

Describe the problem/challenge you have
current output

kapp: Error: Applying create packagemetadata/contour.community.tanzu.vmware.com (data.packaging.carvel.dev/v1alpha1) namespace: default:
  Creating resource packagemetadata/contour.community.tanzu.vmware.com (data.packaging.carvel.dev/v1alpha1) namespace: default: internalpackagemetadatas.internal.packaging.carvel.dev "contour.comm

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:

kubectl schemahero get migrations command can output a long list of migrations, with potentially repeating names.

To find the right migration with a tool like grep, we need to look at the what schema files were changed to determine what the name of the migration would be.

It would be nice to list migrations sorted by timestamps or filter by migration state (open/approved/applied)