An working but restrictive Content-Security-Policy should either be given clearly in the documentation or (even better) set by the argocd server automatically.
A Content-Security-Policy is a basic security measure to protect against cross site scripting attacks.
While I do trust the project to undergo aud
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.
Start up Concourse with default-get-timeout set very low
$ wget https://concourse-ci.org/docker-compose.yml
$ echo " CONCOURSE_DEFAULT_GET
Hi all
We already released the addon-framework where we want to provide out-of the box integrations with third party tools. It would be super helpful if someone familiar with New Relic could assist on building the New Relic integration. The idea is to inform New Relic about changes via [New Relic Custom events](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-apis/introduct
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.
Not sure what the error is, but lint passes in the CI and locally even if exported structs dont have comments.
Most probably, it's an issue with the golangci yaml config we use.
Also we use revive instead of golint (which is deprecated), may be some setting in revive needs to be enabled?
If we check the goreport card, we can see the issues: https://goreportcard.com/report/github.com/jenkins
this command should be something like :
vela env set vela-system --label trivy-scan=true
Then we can tell users that this is a environment for development which can scan vulnerabilities.
Under the hood, we are labeling the k8s namespace.
Originally posted by @wonderflow in kubevela/catalog#380 (comment)
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/
Docker volumes are supported in GH via yaml definitions. We should tell this instead of just throwing an unsupported error.
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
Is your feature request related to a problem? Please describe.
OpenTracing teamed up with OpenCensus to create OpenTelemetry. Tracing support is already stable.
Describe the solution you'd like
Replace OpenTracing with OpenTelemetry tracing. Alternatively, add OpenTelemetry to keep backwards compatibility.
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
As a user, I'd like to know on which day a sequence/task was executed.
In the sequence screen, stages have below them the timestamp of when a sequence was executed for that stage. Similarly, next to the task a timestamp is shown. The format is always HH:MM.
In the best-case, it's usually clear that the sequence was executed within the same day (but you wou
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
https://github.com/google/starlark-go/blob/master/doc/spec.md
It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.
Like in #137 we should provide build context information.
Add a description, image, and links to the continuous-delivery topic page so that developers can more easily learn about it.
To associate your repository with the continuous-delivery topic, visit your repo's landing page and select "manage topics."
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