Giter Club home page Giter Club logo

Comments (7)

jakekaplan avatar jakekaplan commented on June 9, 2024

Hi @pvbhanuteja thanks for filing this issue.

Are you modifying or using a different version or fork of prefect?

The following cli output is not from this codebase:

usage: prefect [--auth_host_name AUTH_HOST_NAME] [--noauth_local_webserver]
               [--auth_host_port [AUTH_HOST_PORT ...]]
               [--logging_level {DEBUG,INFO,WARNING,ERROR,CRITICAL}]

For example this is what I get when I run prefect deploy --help

prefect deploy --help
                                                                                                                                                                                                                                                                            
 Usage: prefect deploy [OPTIONS] [ENTRYPOINT]                                                                                                                                                                                                                               
                                                                                                                                                                                                                                                                            
 Deploy a flow from this project by creating a deployment.                                                                                                                                                                                                                  
 Should be run from a project root directory.                                                                                                                                                                                                                               
                                                                                                                                                                                                                                                                            
╭─ Arguments ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│   entrypoint      [ENTRYPOINT]  The path to a flow entrypoint within a project, in the form of `./path/to/file.py:flow_func_name` [default: None]                                                                                                                        │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
╭─ Options ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --flow                      -f      TEXT     DEPRECATED: The name of a registered flow to create a deployment for. [default: None]                                                                                                                                       │
│ --name                      -n      TEXT     The name to give the deployment. Can be a pattern. Examples: 'my-deployment', 'my-flow/my-deployment', 'my-deployment-*', '*-flow-name/deployment*' [default: None]                                                         │
│ --description               -d      TEXT     The description to give the deployment. If not provided, the description will be populated from the flow's description. [default: None]                                                                                     │
│ --version                           TEXT     A version to give the deployment. [default: None]                                                                                                                                                                           │
│ --tag                       -t      TEXT     One or more optional tags to apply to the deployment. Note: tags are used only for organizational purposes. For delegating work to agents, use the --work-queue flag. [default: None]                                       │
│ --pool                      -p      TEXT     The work pool that will handle this deployment's runs. [default: (from PREFECT_DEFAULT_WORK_POOL_NAME)]                                                                                                                     │
│ --work-queue                -q      TEXT     The work queue that will handle this deployment's runs. It will be created if it doesn't already exist. Defaults to `None`. [default: None]                                                                                 │
│ --variable                  -v      TEXT     One or more job variable overrides for the work pool provided in the format of key=value string or a JSON object [default: None]                                                                                            │
│ --cron                              TEXT     A cron string that will be used to set a CronSchedule on the deployment. [default: None]                                                                                                                                    │
│ --interval                          INTEGER  An integer specifying an interval (in seconds) that will be used to set an IntervalSchedule on the deployment. [default: None]                                                                                              │
│ --anchor-date                       TEXT     The anchor date for all interval schedules [default: None]                                                                                                                                                                  │
│ --rrule                             TEXT     An RRule that will be used to set an RRuleSchedule on the deployment. [default: None]                                                                                                                                       │
│ --timezone                          TEXT     Deployment schedule timezone string e.g. 'America/New_York' [default: None]                                                                                                                                                 │
│ --trigger                           TEXT     Specifies a trigger for the deployment. The value can be a json string or path to `.yaml`/`.json` file. This flag can be used multiple times. [default: None]                                                               │
│ --param                             TEXT     An optional parameter override, values are parsed as JSON strings e.g. --param question=ultimate --param answer=42 [default: None]                                                                                          │
│ --params                            TEXT     An optional parameter override in a JSON string format e.g. --params='{"question": "ultimate", "answer": 42}' [default: None]                                                                                               │
│ --enforce-parameter-schema                   Whether to enforce the parameter schema on this deployment. If set to True, any parameters passed to this deployment must match the signature of the flow.                                                                  │
│ --all                                        Deploy all flows in the project. If a flow name or entrypoint is also provided, this flag will be ignored.                                                                                                                  │
│ --prefect-file                      PATH     Specify a custom path to a prefect.yaml file [default: prefect.yaml]                                                                                                                                                        │
│ --ci                                         DEPRECATED: Please use the global '--no-prompt' flag instead: 'prefect --no-prompt deploy'.                                                                                                                                 │
│                                              Run this command in CI mode. This will disable interactive prompts and will error if any required arguments are not provided.                                                                                               │
│ --help                                       Show this message and exit.                                                                                                                                                                                                 │
╰─────────────────────────────────────────────────────────────────────────

from prefect.

pvbhanuteja avatar pvbhanuteja commented on June 9, 2024

Hey @jakekaplan I'm using the official pip release

from prefect.

jakekaplan avatar jakekaplan commented on June 9, 2024

Do you recognize AUTH_HOST_NAME as something from your own code? We utilize typer for our cli and perhaps some sort of conflict? Additionally does Deploying INFB Daily actually get deployed correctly?

from prefect.

pvbhanuteja avatar pvbhanuteja commented on June 9, 2024

I dont think of any AUTH_HOST_NAME

prefect deploy NAME seems to be working well I have other deployments running following this

image
image

from prefect.

jakekaplan avatar jakekaplan commented on June 9, 2024

It seems like this is coming from google oauth client? do you have that installed/used in your code?

https://oauth2client.readthedocs.io/en/latest/source/oauth2client.tools.html

I am pretty suspicious about the potential Flow naming conflict... but don't understand why this is only happening for the --all argument

https://stackoverflow.com/questions/45172959/how-to-resolve-oauth-cli-argparse-conflicting-with-custom-argparse-arguments

from prefect.

pvbhanuteja avatar pvbhanuteja commented on June 9, 2024

It seems like this is coming from google oauth client? do you have that installed/used in your code?

https://oauth2client.readthedocs.io/en/latest/source/oauth2client.tools.html

I am pretty suspicious about the potential Flow naming conflict... but don't understand why this is only happening for the --all argument

https://stackoverflow.com/questions/45172959/how-to-resolve-oauth-cli-argparse-conflicting-with-custom-argparse-arguments

Exactly I do have Google Oauth installed that might be an issue. But still not sure why this is happening though.

These are my current packages to reproduce it.

  - pip:
      - prefect==2.16.1
      - oauth2client==4.1.3
      - google-api-python-client==2.97.0

from prefect.

jakekaplan avatar jakekaplan commented on June 9, 2024

I'm going to close this issue since it is a problem with oauth2client (which also seems to be deprecated) and not prefect.

It seems oauth2client has an issue taking args that don't belong to it. Heres another example.

If this only happens with --all it is possible one of your files that is getting inspected for flows is using oauth2client not inside of a closure.

from prefect.

Related Issues (20)

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.