I'm just starting out in using DefectDojo, and am a bit confused on what the Tool Type and Tool Configuration sections inside Configuration. I know that documentation is something DefectDojo prides itself on, and I greatly appreciate the breadth of it... but I can't seem to find this documented anywhere.

The regex test if [[ $yml =~ ^(.*/)?secrets(\.[^.]+)*\.yaml$ ]] does not match the helm secrets help text, at least on OSX.

secrets.dev.yaml functions properly; secrets-dev.yaml fails to decrypt; helm secrets implies it should: wrapper that decrypts secrets[.*].yaml

Hi, I would like to know more about what are the internal flows of helmsman. Do you have some design docs ?

It has been removed in favor of operator. Are there still docs from before on how to deploy the helm charts?

Took 58 days to hit the rook-ceph cluster issue again, and I figured I would leave this open until there's the next "days since last accident" event:

jay@home1:/opt/metalnetes$ k get po -n rook-ceph
NAME                                          READY   STATUS             RESTARTS   AGE
rook-ceph-mgr-a-68cb58b456-6m8df              1/1     Running            0          58d
rook-ceph-mon-

Currently trying to configure buildSync.json and I have no idea what is the proper way of configuring the preinstalled buildSync plugin.

at the moment I am getting replication errors for artifactory-build-info and I would like to configure it properly.

Can you please add a checksum annotation for the configmap to force the controller to reload (restart pods) in the case of a config update?

It is redundant to keep Dex Helm chart in this repository, we should leave dex-k8s-authenticator chart and a good explanation of how to integrate it with Dex chart taken from stable/Dex repository.

If

1. You have some questions
2. You had a problem with setup
3. You had a problem with configuration
4. You don't know how to do something
5. Have ideas or propositions
6. Think something could be explained better/in more details

Let me know so I can update documentation, allowing other ppl get over same issues faster.
Please comme

Hello,
I tried to use /bin/terraform-docs.awk to generate documentation with terraform-docs.

An error occured with this variable from provider aws, resource "aws_ecs_service", property "ordered_placement_strategy" :

variable "ordered_placement_strategy" {
  type = list(object({
    type  = string
    field = string
  }))
  description = "Ordered task placement strategy on EC2 inst

Hello,

I just bumped into a little snag trying to use Verdaccio in an environment where it is reverse-proxied with a url_prefix. I thought I'd document what I found; hopefully this is helpful!

summary

In the nginx reverse proxy example with a relative path, the Verdaccio instance at `/verdacc

This commit changed the CRD yaml file names. This can be fixed by pinning to v0.34.0, or changing the referenced filename. I have a change that does the latter if you would like that as a fix. I'd suggest pinning it to v0.34.0 though, and can submit a PR for that instead if desired. There is no tag yet

Issue
Argo CD has runtime flags to change the base context path that content is served on. Currently the Helm chart does not have a mechanism to allow administrators to set this value at deployment time, and the resulting Deployment object needs to be edited by hand.

Proposal
Add an additional flag to the Helm chart that allows the basehref setting to be overridden, and propagate thos

Is this a request for help?:NO

Is this a BUG REPORT or FEATURE REQUEST? (choose one):FEATURE REQUE

The README at https://github.com/cloudposse/charts/blob/0.6.0/incubator/README.md refers to the opsgoodness chart repo at http://charts.opsgoodness.com but that repo does not seem to be working. In fact, it's not clear that this README is actually meant for that directory. It should be fixed if not deleted.

It might be useful to document how to use this on an RBAC enabled cluster and how to create the service account, role, and role binding using the official kubernetes java client.

        ApiClient officialClient = Config.fromUserPassword(
                "https://la-de-do-da"
                 "username",
                 "password"
        );

        CoreV1Api coreV1Api = new CoreV1

This project looks very interesting to me. However, could you add a little more detail documentation on how to, for example, starting with just a dockerfile/helm chart, create an environment. (I mean, I could not even see a 'how to install' section)

We shouldn't leave dirs with names like intent-lynx or jaunty-quail lying around in ~ - we should use something like ~/unfork instead

Thanks for the great examples and starting spot, this is something I could see being immensely helpful for my team and others on leveraging repeatable templates.

One thing to note, the currently deployed version on https://technosophos.github.io/common-chart/ does not contain the updates that were made to some of the core helpers, so it is a bit disorienting when attempting to follow along wit