Is stitch fighting back? Seems they're trying to p...
# random
s
Is stitch fighting back? Seems they're trying to permit more home-grown taps 😆
v
Pretty hard to beat this I think
Copy code
name: pipeline
on: 
 # schedule:
 # Daily at 2am
 # - cron:  '0 2 * * *'
  workflow_dispatch: 
jobs:
  pipeline:
    runs-on: ubuntu-latest
    env:
      python-version: 3.9
    steps:
      - uses: actions/checkout@v2
      - name: Set up Python ${{ env.python-version }}
        uses: actions/setup-python@v2
        with:
          python-version: ${{ env.python-version }}
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install meltano==1.89.0
          meltano install
      - name: Run tap-clickup to target-stitch
        run: meltano elt tap-clickup target-stitch
        env:
          TAP_CLICKUP_API_TOKEN: ${{ secrets.TAP_CLICKUP_API_TOKEN }}
          TARGET_STITCH_CLIENT_ID: ${{ secrets.TARGET_STITCH_CLIENT_ID }} 
          TARGET_STITCH_TOKEN: ${{ secrets.TARGET_STITCH_TOKEN }}
s
And then have it as an import API? Yeah definitely
v
Do it with meltano cloud and you get incremental streams and all that without the action 🙂
Copy code
meltano elt tap-clickup target-stitch
Already imports it to stitch 🤷
But then you quickly ask yourself why am I using stitch?
I like that they added the option there's a ton of folks on their side that struggle with doing custom taps!