Fly problem x509: certificate signed by unknown authority

Hey Community,

I have build up concourse pipelines and would like to do the following in Visual Studio Code:

  1. fly -t <target_name> login -n <team_name> -c <bucc_url> -u -p
  2. Do some GIT Changes to the yml files…
  3. Git add, commit and push
  4. Apply the pipeline: fly -t up -p
  5. Error:
    could not find a valid token.
    logging in to team ‘xxx’

could not reach the Concourse server called xxx:

Get "https://bucc.domain.cloud/api/v1/info": x509: certificate signed by unknown authority

is the targeted Concourse running? better go catch it lol

When i do the step 1.) i also get the error - BUT when i set the option -k then it works, but i cannot set the -k flag:
PS C:\tmp\GIT\pipelines> fly -t -k xxx up -p “xxx”
error: expected argument for flag /t, /target', but got option -k’
PS C:\tmp\GIT\pipelines> fly -t xxx up -p -k “xxx”
error: expected argument for flag /p, /pipeline', but got option -k’

You’re putting the -k flag after other flags that take arguments. Also only fly login takes -k as a flag. I would expect the following to work:

fly -t sometarget login -c example.com -k
# do stuff
fly -t sometarget up -p pipelinename

Thx a lot :slight_smile:
Can you just tell me how to do the following:

  1. Checkout the remote gitlab repo to the local computer ( i have configured and added the workspace to Visual Studio Code).
  2. checkin/Push/Committee the locally changed files to the Remote gitlab
  3. Login with fly to concourse (using option -k to avoid cert 509 errors)
  4. apply the pipeline
  5. unpause the pipeline
  6. run the pipeline

The first two are just a normal git workflow.

  1. fly -t some-target login -c ci.example.com -k
  2. fly -t some-target sp -p pipeline-name -c /path/to/pipeline.yml
  3. fly -t some-target up -p pipeline-name
  4. 3 options:
    a. fly -t some-target tj -j pipeline-name/job-name
    b. trigger the first job in the UI by clicking the +
    c. configure the first job in the pipeline to get the git repo with trigger: true

Note that in Concourse changing the code in git and setting the pipeline are totally separate operations by default.

An alternative workflow is to make the first job in the pipeline do a set_pipeline and trigger automatically off of pushes to the git repo. This is what we do on most of our pipelines. The benefit of this is that you only need to manually run fly set-pipeline when you first create the pipeline and/or if you change the set_pipeline job.