Git Product home page Git Product logo

concourse-fly-resource's People

Contributors

o-orand avatar rskjetlein avatar troykinsella avatar typositoire avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

concourse-fly-resource's Issues

Fly cli execution always executes in team main

At line 50 in out asset:
fly -t main $line
this should probably be
fly -t $team $line

this allows actions against the configured team for the resource instead of always executing in the main team

Insecure SSL certificate support

I am having a pipeline that is using insecure SSL certificate, and I get:

Fetching fly...
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.

I do not see how, I can explain to the fly resource that, and it to use -k when interacting with it.

Run against current team?

I want to use this resource to create self-updating pipelines that might run under multiple teams. It would be very helpful if I could use fly against the current team ($BUILD_PIPELINE_NAME in the resource implementation). I'm guessing that changing the default is undesired as it would break backwards compatibility. Would you consider a pull request to do something like this?

- name: fly
  type: fly
  source:
    url: ((concourse_url))
    username: ((concourse_user))
    password: ((concourse_password))
    use_current_team: true

Unknown command: trigger-job

I'm trying to trigger one job from a different pipeline like

- put: trigger-acceptance-tests
  params:
    options: trigger-job -j acceptance-tests/run-tests

But when I run that in Concourse I get:

error: Unknown command `trigger-job -j acceptance-tests/run-tests'. Please specify one command of: abort-build, builds, check-resource, check-resource-type, checklist, clear-task-cache, containers, curl, delete-target, destroy-pipeline, destroy-team, edit-target, execute, expose-pipeline, format-pipeline, get-pipeline, get-team, help, hide-pipeline, hijack, jobs, land-worker, login, logout, order-pipelines, pause-job, pause-pipeline, pipelines, prune-worker, rename-pipeline, rename-team, resource-versions, resources, set-pipeline, set-team, status, sync, targets, teams, trigger-job, unpause-job, unpause-pipeline, userinfo, validate-pipeline, volumes, watch or workers

If I try with just options: trigger-job I get error: the required flag -j, --job was not specified, so I'm completely baffled as to why this is failing.

I am definitely logged in ok, if I do options: sync then that works fine.

Release ARM64 docker image

I am trying to use concourse-fly-resource docker image over ARM64v8 but it seems it does not have an arm64 supported tag in the docker hub.

I have successfully built the image on arm64 platform.

ARM64 docker Image : https://hub.docker.com/layers/odidev/concourse-fly-resource/latest/images/sha256-9ca79a3abd699efb1f217724cf14c11198dddc166e00f6da653d9b572e33be7f?context=explore

Do you have any plans for releasing an ARM64 image?

May I know how the amd64 image is getting published on Docker hub?

If required, I am happy to help and contribute.

No more basic auth

In 5.2.0 basic auth results in 401 responses from the API, so, the resource fails to get the fly binary from the server
oauth flow will need to be implemented or an alternative source for the fly binary

unknown target: main

Can you clarify in the readme whether the resource logs in by itself or if we need to log in ourselves. It does not seem to create a target, which AFAIK is done on initial login.

resource:

- name: admin-fly
  type: fly
  source:
    url: my.server.duckdns.org
    username: ((concourse_admin_username))
    password: ((concourse_admin_password))
    team: main

put:

  # Apply user configs
  - put: admin-fly
    inputs: all
    params:
      options: set-team -n initial-pipeline-team -c initial-concourse/teams/initial-pipeline-team.yml 

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.