continuous-delivery

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

With a configmap setting like:

  resource.customizations.ignoreDifferences.argoproj.io_Application: |
    jqPathExpressions:
      - '.spec.syncPolicy.automated.al

I think there is a typo here:
https://github.com/concourse/concourse/blob/8e89cfce2b501b408b0cb841e6a2dab77b8ebe13/worker/workercmd/guardian.go#L59

The purpose of this RemoveAll call is to remove existing binaries that are older than it is bundled with. Surely guardian doesn't bundle old binaries :P

s/that/than/

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.

Is it possible to add a check if unleash variable is indeed a json, and disable the option of saving it unless it is?
For example, created a variable for a toggle and selected type to be a json, but I've inserted a string instead of a json and was able to save and pull the value.

{'name': 'test', 'payload': {'type': 'json', 'value': 'not a json'}, 'weightType': 'variable', 'enabled': True}

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

Environment

Liquibase Version:
4.1.0
Also latest master

Liquibase Integration & Version:
gradle, unknown version

Liquibase Extension(s) & Version:

Database Vendor & Version:
PostgreSQL: 12.X (occurs on all supported versions)

Operating System Type & Version:
MacOS 11.4 (20F71), but will occur on all supported OSs

Description

A clear and concis

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.

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

Environment

• Client OS (e.g., Linux, macOS, Windows): any
• Keptn Version (keptn version): 0.9.2
• Kubernetes Cloud Provider (e.g., GKE, AKS): any
• Kubernetes version (kubectl version): any

Affected Component

• Docs
• CLI
• Kubernetes Integration
• Openshift Integration
• Helm
• Istio
• Bridge
• Approval
• Datastore
• REST

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