POC for running GitHub Actions or Orbs from the Gitlab-ci.yml file

Problem to solve

We want to be able to run GitHub actions and/or Circle CI orbs from GitLab

Intended users

Further details

build: 
  image: ubuntu-latest   
  script:     
    - uses: actions/checkout@sha256       
      with:         
        - my_config     
    - uses: setup-node @SHA256   
    - npm install     
    - npm publish  

 build2:   
  image: ubuntu-latest   
  script:     
    - uses: actions/aws_builder:sha256       
      with:         
        - aws_secret: $AWS_SECRET       
        - aws_username: $AWS_USERNAME

GitHub Actions (How we think it would be interpreted to .gitlab-ci.yml) https://gitlab.com/gitlab-org/gitlab/uploads/4feb5d04baef38b7450943f406043b42/image.png

GitHub Actions (How we think it would be interpreted to .gitlab-ci.yml with AWS variables)

Circle CI Orbs (How we think it would be interpreted to .gitlab-ci.yml)

Recording of discussion of AWS deployments https://gitlab.zoom.us/rec/share/38hMDevhyEdObqvfsGWGQLcbPa39X6a81SgXqacOyPkJC98pL-aFwzYUk5CnwpY

Proposal

The purpose of this issue is to successfully run a GitHub action or Circle CI orb from the .gitlab-ci.yml file.

Steps of the POC:

Decide which method is easier and more compatible with .gitlab-ci.yml
Select an action/orb with intermediate complexity (transferring parameters)
Successfully running the action/orb directly to/from AWS
Create documentation of what is needed in order to use actions/orbs from the .gitlab-ci.yml, including which environment variables and secrets

POC for running GitHub Actions or Orbs from the Gitlab-ci.yml file

Problem to solve

Intended users

Further details

Proposal

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references