Config:

linters:
  disable-all: true
  enable:
  - goimports
  - gci
  fast: false

linters-settings:
  goimports:
    local-prefixes: istio.io/

Input:

package main

import (
	"fmt"
	"istio.io/istio/pkg/test/framework/resource"
	"os"

	"istio.io/istio/pkg/test/framework/resource"
)

var (
	_ = resource.Cluster
	_ = fmt.Println
	_ = os.Stdout
)

Goal

Implement --team for remaining fly commands. fly/integration tests should be updated. Cases should be added to the error_handling file as well https://github.com/concourse/concourse/blob/587483424a47f3eebb2ed8e861687b60cccb9ec7/fly/integration/error_handling_test.go#L92

# use default team
fly -t ci <command> <command-options>
# use another team
fly -t ci <command>

JanitorConfigurator should have an option to delete logs for specific builders (or tags). Users might want to delete logs for only specific builders, or might want to keep logs for specific builders for longer duration.

http://docs.buildbot.net/latest/manual/cfg-configurators.html#janitorconfigurator currently doesn't seems to contain any such option.

Describe the bug
This resource causes the error WARNING: skipped AWS017 check due to error(s): value is null

And it happens even if I try to explicit skip AWS017 from cli:

tfsec --exclude AWS017
WARNING: skipped AWS017 check due to error(s): value is null

tfs

I would welcome a feature when, at the same url which is set to respond with OK status, I could have an error response generated with a random seed.

I am developing an Observable pattern to perform a series of retries to call an endpoint, with increasing delay. The problem is that during testing, I cannot really mock up the condition by randomly switching between two mocky.io urls (error and ok