The (still undocumented) feature is great for our purpose, but can you add the same functionality to the post-update hook (in the same manner, of course)?

I have added a script to the post-update to check the database-version. If they not match, the script returns exit 1. It would be great if the post-update hook could log a error- or warning-message, so the slack-notification gets a message (l

Summary

For some reason ARGOCD_GIT_MODULES_ENABLED must be set directly on the repo-server Deployment instead of being set in the argocd-cmd-params-cm ConfigMap like most env vars. It should be configurable in that ConfigMap, and the new way of configuring it should be documened.

Motivation

Not following the pattern [causes confusion](https://cloud-native.slack.com/archives/C01TSERG

Summary

If there is a global default-get-timeout set on the web node, it is not possible to override that timeout for the implicit get step that is used to pull the image_resource configured on a task.

Steps to reproduce

Start up Concourse with default-get-timeout set very low

$ wget https://concourse-ci.org/docker-compose.yml

$ echo "      CONCOURSE_DEFAULT_GET

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.

When inputting values with jx secret edit you can't input multiline values. I'm trying to edit jenkins-maven-settings.

Addon is actually a bunch of yaml, it will help you deploy. What if we have a command that help render these yamls:

vela addon enable velaux --dry-run

And it prints all those yamls, then you can apply them?

vela addon enable velaux --dry-run > addon-manifest.yaml
kubectl apply -f addon-manifest.yaml

_Originally posted by @wonderflow in https://github.com/kubevela/k

In #2649, all our dependencies except this module in the Azure related end-to-end tests were updated, as it contains a breaking change.

tfinstall has been removed and needs to be replaced with https://github.com/hashicorp/hc-install. We call it exactly one time in [azure_test.go](https://github.com/

When there are not enough results, we tell the user that the experiment just started, so come back later. When the experiment dates are set to a future time, this language doesn't fit very well. We should adjust the language to take this future state into account when figuring out the message.

<img width="875" alt="CleanShot 2022-04-10 at 21 23 22@2x" src="https://user-images.githubusercontent

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

Environment

Liquibase Version: 4.6.1

Liquibase Integration & Version: 4.6.1

Liquibase Extension(s) & Version: 4.6.1

Database Vendor & Version: MySQL8.0.27

Operating System Type & Version: MacOS Monterey 12.0.1

Descript

Upgrade Dockerfiles, build and all workflows to use go 1.18

Is your enhancement proposal related to a problem? Please describe.
For now, there are no connectivity test for jira integration. This will cause problem if the user is integrating with the wrong credential.

Describe the solution you'd like
Add a connectivity test API for jira integration which will take the integration info as input and returns if the API call to jira can be made suc

The bridge username appears hardcoded to keptn. This issue is to make it configurable at install via helm.

I believe the correct place is here: https://github.com/keptn/keptn/blob/55db322e351d0b94ae0e63a767191f83f820736f/installer/manifests/keptn/templates/core.yaml#L55

@StackScribe please tag as a good first issue