An Action to set up duplocloud cli and the underlying cloud. During this process, duplo discovers the underlying cloud which is either aws, gcp, or azure. Once the cloud is known, the corresponding cli is installed. Finally the action will authenticate with the cloud provider. It provides the following features:

• Setting up Python.
• Installing duploctl.
• when AWS
  • Installing AWS CLI.
  • Running Duplo JIT (Just-In-Time) for AWS.
  • Configuring AWS IAM Credentials.
• when GCP
  • Installing GCP CLI.
  • Configuring GCP SA Credentials.
• when Azure
  • Installing Azure CLI.
  • Configuring Azure SCP Credentials.

The following input variables can be configured:

AWS Example:

name: Simple AWS Setup
on: 
- push
jobs:
  build:
    runs-on: ubuntu-latest
    env:
      DUPLO_TOKEN: ${{ secrets.DUPLO_TOKEN }}
      DUPLO_HOST: ${{ vars.DUPLO_HOST  }}
      DUPLO_TENANT: ${{ vars.DUPLO_TENANT }}
    steps:
    - name: Duplo Setup
      uses: duplocloud/actions/setup@main

GCP or Azure Example:
The only difference is there is no JIT for GCP or Azure. This means the job needs to have some pre-configured credentials to use for authentication. The name of the account is required for GCP and Azure as well.

steps:
- name: Duplo Setup
  uses: duplocloud/actions/setup@main
  with:
    account-id: ${{ vars.CLOUD_ACCOUNT }}
    credentials: ${{ secrets.CLOUD_CREDENTIALS }}

Each underlying cloud has their own unique way of authenticating.

Using the JIT functionality built into the portal, the action uses retreives an sts session from the duplo portal and uses these credentials to authenticate with the AWS CLI. Magical.

The action uses the azure/login action to authenticate with Azure. To keep things consistent this action will use the CLOUD_CREDENTIALS secret to authenticate which expects the following format:

{
  "clientId": "<client-id>",
  "clientSecret": "<client-secret>",
  "subscriptionId": "<subscription-id>",
  "tenantId": "<tenant-id>"
}

The action uses the google-github-actions/setup-gcloud action to authenticate with GCP. To keep things consistent this action will use the CLOUD_CREDENTIALS secret to authenticate which expects the following format:

{
  "type": "service_account",
  "project_id": "<project-id>",
  "private_key_id": "<private-key-id>",
  "private_key": "<private-key>",
  "client_email": "<client-email>",
  "client_id": "<client-id>",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://accounts.google.com/o/oauth2/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "<client-x509-cert-url>"
}

The scripts and documentation in this project are released under the MIT License.

• Third Party Actions:
  • aws-actions/configure-aws-credentials@v3
  • unfor19/install-aws-cli-action@v1
  • actions/setup-python@v5
  • google-github-actions/setup-gcloud
  • google-github-actions/auth
  • azure/login
  • azure/CLI