Summary

Many users run Argo CD in a mode where that Argo CD instance doesn't ever need or want to deploy Applications to the same cluster Argo CD is running in (e.g. Intuit does this). For these users, the https://kubernetes.default.svc should be disabled and removed as an option.

Motivation

The ability to disable https://kubernetes.default.svc is both a security improvement as wel

Summary

Running fly execute --tag=asdf --input jkl=. will fail without a specific error message if a worker with tag asdf is not available at the time the command is executed.

Steps to reproduce

Task config:

---
platform: linux

image_resource:
  type: registry-image
  source:
    repository: alpine

inputs:
- name: source

run:
  path: sh
  args:
  - -e

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.4.3

Liquibase Integration & Version: quarkus 2.3.0.Final

Liquibase Extension(s) & Version: liquibase-core only

Database Vendor & Version: MariaDB 10.6.4

Operating System Type & Version: Windows

Use CML_TOKEN instead of REPO_TOKEN to

• avoid potential namespace clashes
• better reflect that it could be a project token, org token, bot token, encoded username & password, etc
• better reflect that it's mostly used to launch runners and also is used by runners

• from iterative/cml.dev#122 (comment)
• related #738, #741, #712

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)

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

• A remediation sequence gets triggered using:

{
  "data": {
    "labels": {
      "Problem URL": "https:///#problems/problemdetails;pid=-240816790436828345_1633506659151V2"
    },
    "problem": {
      "ProblemTitle": "Http monitor global outage",
    },
    "project": "musicshop",
    "service": "carts",
    "stage": "production"
  },
  "id": "d485ea90-e1ef-4ce2-af21-32