the SSE feed should cache repository permissions to reduce database lookups. There are no documented issues of this being a problem, but this sort of performance improvements seems like low hanging fruit.

Installation method "Method

In order to make the UI/UX consistent across all pages of GoCD, GoCD is rebuilding the Pipeline Config Edit Page (changing into a Single Page App).

As part of this page rewrite, following changes needs to be done on the plugins:

Breaking Changes

Task Plugins View:

GoCD Task Plugins implements Get Task View extension call, which

What challenge are you facing?

The help text for fly order-pipelines:

Usage:
  fly [OPTIONS] order-pipelines [order-pipelines-OPTIONS]

Application Options:
  -t, --target=              Concourse target name
  -v, --version              Print the version of Fly and exit
      --verbose              Print API requests and responses
      --print-table-headers  Print table heade

When deploying hasura example - mono repo with k8s, git push is failing with

$ git push minikube master
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

When creating myremote, I have used ~/.ssh/id_ras.pub and it wasn't changed. Not sure wh

Summary

Add field/label "LIVE For:" to show how much time the Revision was LIVE. Currently when a user clicks on the "History and Rollback", it shows all past Revisions and when it was triggered and completed and also displays the amount of time for which that Revision was LIVE. But it does not mention what these timings/durations are for (as shown in the attached screenshot where it shows dur

If it already is, it serves two masters (which isn't clear).

e.g. better documentation for self-signed certs

On the basis of Review Russian documentation #1963

• Main
• README
• Documentation Overview
• Configuration / Introduction
• Configuration / Dockerfile image
• Configuration / Stapel Image / Naming
• Configuration / Stapel Image / Base Image
• Configuration / Stapel Image / Docker directive
• Confi

I would like to see documentation for using Astra with most popular authentication/token methods. So much work but just one page of documentation. Please update this so it gets more widely used and more feedback on the product this way. Thanks

TL;DR; This:

habitus -use-tls --build host=$(ipconfig getifaddr en0) --binding=$(ipconfig getifaddr en0) --secrets=true

Better to note somewhere in the habitus doc based on my own experience 😉

What happened:
Shared commands expire due to a side effect of using catbox-s3 for uploading to AWS. Cluster admins must set an expiry time and users suffer if they don't have period builds.

What you expected to happen:
This life cycle for shared command is arbitrary and Screwdriver should not be in the business of policing how long should command owners rebuild the commands and forc

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.

I tried using customConfig but it fails because it tries to load the yml files from a library.

Create a simple dummy task, to make it easier to play with Glue and understand it's features. The task should generate some findings, with different levels.

The official docs site seems to be out of date. For example, while a document for the PSGalleryScript deployment option was added a year ago, it does not exist in the published docs.

I see we're using RTD for docs hosting, perhaps the link to t