Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serverless triggers are not being deployed #1474

Open
davidsbond opened this issue Dec 19, 2023 · 4 comments
Open

Serverless triggers are not being deployed #1474

davidsbond opened this issue Dec 19, 2023 · 4 comments
Labels
bug do-api Depends on additional features for the DigitalOcean API

Comments

@davidsbond
Copy link

davidsbond commented Dec 19, 2023

Describe the Issue:

Hi! I'm trying to use doctl to deploy a serverless function with a cron trigger. When I run the doctl serverless deploy command my function is deployed but the trigger is not. I do not see a section in my console output for the trigger.

Environment:

  • doctl version: 1.101.0-release
  • OS: Ubuntu
  • Installation method: Snap

Additional Details:

Adding a trace flag provides no additional output. My project file looks like this:

packages:
  - name: jobs
    shared: false
    functions:
       - name: test
         runtime: go:default
         web: false
         triggers:
           - name: cron-trigger
             sourceType: scheduler
             sourceDetails:
               cron: "0 12 * * *"
               withBody: {}
@davidsbond davidsbond added the bug label Dec 19, 2023
@davidsbond
Copy link
Author

Ah, it seems like scheduling doesn't work with go functions. Is this intended behaviour?

@andrewsomething
Copy link
Member

@davidsbond I've confirmed with the Serverless team that it is currently the expected behavior. Unfortunately, triggers are not deployed when using remote builds and Go functions are always remote builds. Triggers can be used with Go functions, but they must be created in the control panel for now.

Let's keep this issue open for tracking. Even though it is the current behavior, it is something we should support in the future.

@steevehook
Copy link

steevehook commented Dec 31, 2023

The Digital Ocean cripling signature. Waiting for a product that actually works as expected

@pippinmole
Copy link

Hi,

I'm getting the same behaviour, but with python cron jobs.

packages:
  - name: my_package
    functions:
      - name: my_name
        runtime: python:3.11
        limits:
          memory: 512 # MB
        triggers:
          - name: cron-trigger
            sourceType: scheduler
            sourceDetails:
              cron: "0/15 * * * *" # every 15 minutes

Running:

doctl serverless deploy . --remote-build

And it's not showing up in the dashboard:

image

Environment:

doctl version: 1.103.0-release
OS: Windows

Really looking forward to this being fixed :)

@andrewsomething andrewsomething added the do-api Depends on additional features for the DigitalOcean API label Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug do-api Depends on additional features for the DigitalOcean API
Projects
None yet
Development

No branches or pull requests

4 participants