A cross platform CLI for Flyte. Written in Golang. Offers an intuitive interface to Flyte https://flytectl.readthedocs.io/en/latest/

Overview

Flyte Logo

FlyteCTL

Flyte's official command-line interface

Documentation ยท Contribution Guide

Docs Current Release Master GoDoc License CodeCoverage Go Report Card Commit activity Commit since last release Slack

FlyteCTL was designed as a portable and lightweight command-line interface to work with Flyte. It is written in Golang and accesses FlyteAdmin, the control plane for Flyte.

๐Ÿš€ Quick Start

  1. Install FlyteCTL with bash or shell script

    • Bash
      $ brew install flyteorg/homebrew-tap/flytectl
    • Shell script
      $ curl -sL https://ctl.flyte.org/install | bash
  2. (Optional) flytectl upgrade provides a general interface to upgrading FlyteCTL; run the command in the output

  3. Start sandbox using FlyteCTL

    $ flytectl sandbox start 
  4. Register examples

    # Register core workflows 
    $ flytectl register examples -d development -p flytesnacks

๐Ÿ“– How to Contribute to FlyteCTL

You can find the detailed contribution guide here.

๐Ÿž File an Issue

Refer to the issues section in the contribution guide if you'd like to file an issue.

Comments
  • [Docs] Flytectl docs cleanup

    [Docs] Flytectl docs cleanup

    Read then delete

    • Make sure to use a concise title for the pull-request.
    • Use #patch, #minor #majora or #none in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details

    TL;DR

    This PR attempts to cleanup docs of flytectl (like-: grammer, punctuations etc.)

    Type

    • [ ] Bug Fix
    • [ ] Feature
    • [ ] Plugin
    • [x] Docs

    Are all requirements met?

    • [ ] Code completed
    • [ ] Smoke tested
    • [ ] Unit tests added
    • [ ] Code documentation added
    • [ ] Any pending items have an associated Issue

    Complete description

    Cleaning docs of flytectl. Files cleaned-: (Still adding Files) flytectl/docs/source/gen/flytectl.rst

    Tracking Issue

    https://github.com/flyteorg/flyte/issues/

    Follow-up issue

    NA OR https://github.com/flyteorg/flyte/issues/1524

    opened by abhijeet007rocks8 27
  • [Hacktoberfest] Copy-edited FlyteCTL docs

    [Hacktoberfest] Copy-edited FlyteCTL docs

    TL;DR

    The PR fixes all of the grammatical problems and other problems of one third of the docs in the general section.

    Type

    • [ ] Bug Fix
    • [ ] Feature
    • [ ] Plugin
    • [x] Docs

    Are all requirements met?

    • [ ] Code completed
    • [ ] Smoke tested
    • [ ] Unit tests added
    • [ ] Code documentation added
    • [ ] Any pending items have an associated Issue

    Complete description

    I have copyedited one third of all the docs in the general section. I have fixed the punctuation errors and other grammatical errors.

    Tracking Issue

    https://github.com/flyteorg/flyte/issues/1524

    Follow-up issue

    NA OR https://github.com/flyteorg/flyte/issues/

    opened by Sayanta66 20
  • Compile command

    Compile command

    TL;DR

    Adding a compile cmd to let users validate workflows without registration.

    Type

    • [ ] Bug Fix
    • [x] Feature
    • [ ] Plugin

    Are all requirements met?

    • [x] Code completed
    • [ ] Smoke tested
    • [x] Unit tests added
    • [ ] Code documentation added
    • [ ] Any pending items have an associated Issue

    Complete description

    Usage: flytectl compile --file flyte-package.tgz Output sample:

    Successfuly extracted package...
    Processing Protobuff files...
    Task: /tmp/register829973350/0_example.example.generate_normal_df_1.pb
    Task: /tmp/register829973350/1_example.example.compute_stats_1.pb
    Workflow: /tmp/register829973350/2_example.example.wf_2.pb
    Launch Plan: /tmp/register829973350/3_example.example.wf_3.pb
    Compiling tasks...
    Compiling workflow: example.example.wf
    All Workflows compiled successfully!
    
    Summary:
    1  workflows found in package
    2  Tasks found in package
    1  Launch plans found in package
    

    Important changes:

    • Imported flytepropeller's compiler (thus changes in go.mod)
    • upgraded Go from 1.17 -> 1.18 (this is needed as flytepropeller seems to use a library that does not work with 1.17)
    • Added a new command to cobra (compile)
    • Added some minimal tests

    Tracking Issue

    https://github.com/flyteorg/flyte/issues/2141

    Follow-up issue

    NA

    opened by dav009 12
  • Visualize graphs on command line

    Visualize graphs on command line

    Signed-off-by: Ketan Umare [email protected]

    TL;DR

    Uses graphviz to visualize flyte workflows on commandline. Example of branch node nested-conditionals coin-toss sub-workflows

    Type

    • [ ] Bug Fix
    • [x] Feature
    • [ ] Plugin

    Are all requirements met?

    • [x] Code completed
    • [x] Smoke tested
    • [x] Unit tests added
    • [x] Code documentation added
    • [x] Any pending items have an associated Issue

    Complete description

    Uses graphviz to visualize flyte workflows on commandline

    opened by kumare3 12
  • Copyedited the document

    Copyedited the document

    Read then delete

    • Make sure to use a concise title for the pull-request.
    • Use #patch, #minor #majora or #none in the pull-request title to bump the corresponding version. Otherwise, the patch version will be bumped. More details

    TL;DR

    Please replace this text with a description of what this PR accomplishes.

    Type

    • [ ] Bug Fix
    • [ ] Feature
    • [ ] Plugin
    • [x] Docs

    Are all requirements met?

    • [ ] Code completed
    • [ ] Smoke tested
    • [ ] Unit tests added
    • [ ] Code documentation added
    • [ ] Any pending items have an associated Issue

    Complete description

    I fixed the documentation with punctuation error and verbal errors.

    Tracking Issue

    https://github.com/flyteorg/flyte/issues/

    Follow-up issue

    NA OR https://github.com/flyteorg/flyte/issues/

    opened by Sayanta66 11
  • Added update for named entity

    Added update for named entity

    Signed-off-by: Prafulla Mahindrakar [email protected]

    TL;DR

    Following command updates the description on the workflow.

     flytectl update workflow -p flytectldemo -d development core.advanced.run_merge_sort.merge_sort --description "Mergesort workflow example"
    

    Archiving workflow named entity would cause this to disapper from flyteconsole UI.

     flytectl update workflow -p flytectldemo -d development  core.advanced.run_merge_sort.merge_sort --archive
    

    Activating workflow named entity would unarchive it.

     flytectl update workflow -p flytectldemo -d development  core.advanced.run_merge_sort.merge_sort --activate
    

    Following command updates the description on the task.

     flytectl update  task -d development -p flytectldemo core.advanced.run_merge_sort.merge --description "Merge sort example"
    

    Archiving task named entity would is not supported and would throw an error.

     flytectl update  task -d development -p flytectldemo core.advanced.run_merge_sort.merge --archive
    

    Activating workflow named entity would be a noop as archiving is not possible.

     flytectl update  task -d development -p flytectldemo core.advanced.run_merge_sort.merge --activate
    

    Following command updates the description on the launchplan.

     flytectl update launchplan -p flytectldemo -d development  core.advanced.run_merge_sort.merge_sort --description "Mergesort example"
    

    Archiving launchplan named entity is not supported and would throw an error.

     flytectl update launchplan -p flytectldemo -d development  core.advanced.run_merge_sort.merge_sort --archive
    

    Activating launchplan named entity would be a noop.

     flytectl update launchplan -p flytectldemo -d development  core.advanced.run_merge_sort.merge_sort --activate
    

    Type

    • [ ] Bug Fix
    • [X] Feature
    • [ ] Plugin

    Are all requirements met?

    • [X] Code completed
    • [ ] Smoke tested
    • [X] Unit tests added
    • [ ] Code documentation added
    • [ ] Any pending items have an associated Issue

    Complete description

    How did you fix the bug, make the feature etc. Link to any design docs etc

    Tracking Issue

    https://github.com/flyteorg/flyte/issues/919

    Follow-up issue

    opened by pmahindrakar-oss 11
  • #minor Node executions

    #minor Node executions

    TL;DR

    Adds node execution details on the execution view

    Gets the details in the tree view. This is the default view for details which fetch the node exeuction details and task executions on each node.

    1] Default is tree view and table format is not supported for this explicitly

    flytectl get execution -p flytectldemo -d development f3a5a4034960f4aa1a09 --details
    
    TABLE format is not supported on detailed view and defaults to tree view. Choose either json/yaml
    Node Executions
    โ””โ”€โ”€ start-node - SUCCEEDED - 1970-01-01 00:00:00 +0000 UTC - 1970-01-01 00:00:00 +0000 UTC
    โ””โ”€โ”€ n1 - SUCCEEDED - 2021-06-30 08:51:07.3111846 +0000 UTC - 2021-06-30 08:51:17.192852 +0000 UTC
    โ”‚   โ”œโ”€โ”€ Attempt :0
    โ”‚       โ””โ”€โ”€ Task - SUCCEEDED - 1970-01-01 00:00:00 +0000 UTC - 1970-01-01 00:00:00 +0000 UTC
    โ”‚       โ””โ”€โ”€ Task Type - 
    โ”‚       โ””โ”€โ”€ Reason - 
    โ”‚       โ””โ”€โ”€ Logs :
    โ”‚           โ””โ”€โ”€ Name :Kubernetes Logs (User)
    โ”‚           โ””โ”€โ”€ URI :http://localhost:30082/#/log/flytectldemo-development/f3a5a4034960f4aa1a09-n1-0/pod?namespace=flytectldemo-development
    โ””โ”€โ”€ n0 - SUCCEEDED - 2021-06-30 08:49:01.582546 +0000 UTC - 2021-06-30 08:51:07.1850111 +0000 UTC
    โ”‚   โ”œโ”€โ”€ Attempt :0
    โ”‚       โ””โ”€โ”€ Task - SUCCEEDED - 1970-01-01 00:00:00 +0000 UTC - 1970-01-01 00:00:00 +0000 UTC
    โ”‚       โ””โ”€โ”€ Task Type - 
    โ”‚       โ””โ”€โ”€ Reason - 
    โ”‚       โ””โ”€โ”€ Logs :
    โ”‚           โ””โ”€โ”€ Name :Kubernetes Logs (User)
    โ”‚           โ””โ”€โ”€ URI :http://localhost:30082/#/log/flytectldemo-development/f3a5a4034960f4aa1a09-n0-0/pod?namespace=flytectldemo-development
    โ””โ”€โ”€ end-node - SUCCEEDED - 1970-01-01 00:00:00 +0000 UTC - 1970-01-01 00:00:00 +0000 UTC
    

    2] Yaml view for the details

    flytectl get execution -p flytectldemo -d development f3a5a4034960f4aa1a09 --details  -o yaml
    - closure:
        createdAt: "2021-06-30T08:51:17.271218200Z"
        phase: SUCCEEDED
        updatedAt: "2021-06-30T08:51:17.311695100Z"
      id:
        executionId:
          domain: development
          name: f3a5a4034960f4aa1a09
          project: flytectldemo
        nodeId: end-node
      inputUri: s3://my-s3-bucket/metadata/propeller/flytectldemo-development-f3a5a4034960f4aa1a09/end-node/data/inputs.pb
      metadata:
        specNodeId: end-node
    - closure:
        createdAt: "2021-06-30T08:49:01.528398300Z"
        duration: 125.602465100s
        outputUri: s3://my-s3-bucket/metadata/propeller/flytectldemo-development-f3a5a4034960f4aa1a09/n0/data/0/outputs.pb
        phase: SUCCEEDED
        startedAt: "2021-06-30T08:49:01.582546Z"
        updatedAt: "2021-06-30T08:51:07.185011100Z"
      id:
        executionId:
          domain: development
          name: f3a5a4034960f4aa1a09
          project: flytectldemo
        nodeId: n0
      inputUri: s3://my-s3-bucket/metadata/propeller/flytectldemo-development-f3a5a4034960f4aa1a09/n0/data/inputs.pb
      metadata:
        specNodeId: n0
    - closure:
        createdAt: "2021-06-30T08:51:07.249937800Z"
        duration: 9.881667400s
        outputUri: s3://my-s3-bucket/metadata/propeller/flytectldemo-development-f3a5a4034960f4aa1a09/n1/data/0/outputs.pb
        phase: SUCCEEDED
        startedAt: "2021-06-30T08:51:07.311184600Z"
        updatedAt: "2021-06-30T08:51:17.192852400Z"
      id:
        executionId:
          domain: development
          name: f3a5a4034960f4aa1a09
          project: flytectldemo
        nodeId: n1
      inputUri: s3://my-s3-bucket/metadata/propeller/flytectldemo-development-f3a5a4034960f4aa1a09/n1/data/inputs.pb
      metadata:
        specNodeId: n1
    - closure:
        createdAt: "2021-06-30T08:49:01.491365700Z"
        phase: SUCCEEDED
        updatedAt: "2021-06-30T08:49:01.491365700Z"
      id:
        executionId:
          domain: development
          name: f3a5a4034960f4aa1a09
          project: flytectldemo
        nodeId: start-node
      inputUri: s3://my-s3-bucket/metadata/propeller/flytectldemo-development-f3a5a4034960f4aa1a09/start-node/data/inputs.pb
      metadata:
        specNodeId: start-node
    

    3] Default tree view for task executions in a node provide a name of the node.

    flytectl get execution -p flytectldemo -d development f3a5a4034960f4aa1a09 --details  --nodeId n0
    TABLE format is not supported on detailed view and defaults to tree view. Choose either json/yaml
    Task Executions
    โ””โ”€โ”€ Attempt :0
        โ””โ”€โ”€ Task - SUCCEEDED - 1970-01-01 00:00:00 +0000 UTC - 1970-01-01 00:00:00 +0000 UTC
        โ””โ”€โ”€ Task Type - 
        โ””โ”€โ”€ Reason - 
        โ””โ”€โ”€ Logs :
            โ””โ”€โ”€ Name :Kubernetes Logs (User)
            โ””โ”€โ”€ URI :http://localhost:30082/#/log/flytectldemo-development/f3a5a4034960f4aa1a09-n0-0/pod?namespace=flytectldemo-development
    

    4] Yaml representation for the same task executions.

    flytectl get execution -p flytectldemo -d development f3a5a4034960f4aa1a09 --details  --nodeId n0 -o yaml
    closure:
      createdAt: "2021-06-30T08:49:01.573698800Z"
      logs:
      - messageFormat: JSON
        name: Kubernetes Logs (User)
        uri: http://localhost:30082/#/log/flytectldemo-development/f3a5a4034960f4aa1a09-n0-0/pod?namespace=flytectldemo-development
      outputUri: s3://my-s3-bucket/metadata/propeller/flytectldemo-development-f3a5a4034960f4aa1a09/n0/data/0/outputs.pb
      phase: SUCCEEDED
      updatedAt: "2021-06-30T08:51:07.169958100Z"
    id:
      nodeExecutionId:
        executionId:
          domain: development
          name: f3a5a4034960f4aa1a09
          project: flytectldemo
        nodeId: n0
      taskId:
        domain: development
        name: core.control_flow.subworkflows.t1
        project: flytectldemo
        resourceType: TASK
        version: v3
    inputUri: s3://my-s3-bucket/metadata/propeller/flytectldemo-development-f3a5a4034960f4aa1a09/n0/data/inputs.pb
    

    Type

    • [ ] Bug Fix
    • [x] Feature
    • [ ] Plugin

    Are all requirements met?

    • [x] Code completed
    • [x] Smoke tested
    • [x] Unit tests added
    • [x] Code documentation added
    • [ ] Any pending items have an associated Issue

    Complete description

    How did you fix the bug, make the feature etc. Link to any design docs etc

    Tracking Issue

    https://github.com/flyteorg/flyte/issues/1124

    Follow-up issue

    NA OR https://github.com/lyft/flyte/issues/

    opened by pmahindrakar-oss 10
  • rename to flyteorg from lyft org, for flytectl

    rename to flyteorg from lyft org, for flytectl

    TL;DR

    Starting to update references to flyteorg

    Type

    • [x] Bug Fix

    Are all requirements met?

    • [x] Code completed

    Complete description

    Changed reference links

    Tracking Issue

    https://github.com/lyft/flyte/issues/729

    opened by brucearctor 10
  • Added Create command

    Added Create command

    TL;DR

    1] Added new command named create

    flytectl is CLI tool written in go to interact with flyteadmin service
    
    Usage:
      flytectl [command]
    
    Available Commands:
      config      Runs various config commands, look at the help of this command to get a list of available commands..
      create      Used for creating various flyte resources including tasks/workflows/launchplans/executions/project.
      get         Used for fetching various flyte resources including tasks/workflows/launchplans/executions/project.
      help        Help about any command
      register    Registers tasks/workflows/launchplans from list of generated serialized files.
      update      
    Used for updating flyte resources eg: project.
    
      version     Displays version information for the client and server.
    
    1. Added Project sub command for create
    Example create.
    ::
    
     bin/flytectl create project
    
    Usage:
      flytectl create [command]
    
    Available Commands:
      project     Create project resources
    
    1. Added create project command
    Usage:
      flytectl create project [flags]
    
    Aliases:
      project, projects
    
    Flags:
          --description string      description for the project specified as argument.
          --file string             file for the project definition.
      -h, --help                    help for project
          --id string               id for the project specified as argument.
          --labels stringToString   labels for the project specified as argument. (default [])
          --name string             name for the project specified as argument.
    

    Type

    • [ ] Bug Fix
    • [ ] Feature
    • [ ] Plugin

    Are all requirements met?

    • [ ] Code completed
    • [ ] Smoke tested
    • [ ] Unit tests added
    • [ ] Code documentation added
    • [ ] Any pending items have an associated Issue

    Complete description

    Screenshot 2021-02-17 at 11 19 35 PM

    Screenshot 2021-02-17 at 10 28 11 PM

    Tracking Issue

    https://github.com/lyft/flyte/issues/

    Follow-up issue

    NA OR https://github.com/lyft/flyte/issues/

    opened by evalsocket 10
  • Added sandbox command

    Added sandbox command

    TL;DR

    Introduce new command for making sandbox and serializing experience smooth

    $ flytectl sandbox start # it will create sandbox and setup your flytectl/kubectl config. it also clone flytesnack repo
    $ flytectl sandbox teardown # It will cleanup flyte sandbox env 
    $ flytectl register examples/flytesnack # it will use flytesnacks release to read flyte_test_manifest and register all workflow available in the cluster. 
    

    logs :

    18:16:59 โžœ flytectl go run main.go sandbox start   
    INFO[0000] Using config file: [config.yaml]             
    ๐Ÿš€ It will take some time, We will start a fresh flyte cluster for you
    {"status":"Pulling from flyteorg/flyte-sandbox","id":"dind"}
    {"status":"Digest: sha256:05554e3ed90e2a009192f02150fce5cd007bb0f857712f11b789996929002752"}
    {"status":"Status: Image is up to date for ghcr.io/flyteorg/flyte-sandbox:dind"}
    Starting Docker daemon...
    Done.
    Starting k3s cluster...
    Done.
    Deploying Flyte...
    ...
    ...
    ...
    -deployment.apps/flytepropeller condition met
    ๐Ÿ‘จโ€๐Ÿ’ป Flyte is ready! Flyte UI is available at http://localhost:30081/console. ๐Ÿš€ ๐Ÿš€ ๐ŸŽ‰ 
    Please visit https://github.com/flyteorg/flytesnacks ๐Ÿš€ 
    Register all flytesnacks example  'flytectl register examples  -d development  -p flytesnacks
    
    

    Type

    • [ ] Bug Fix
    • [x] Feature
    • [ ] Plugin

    Are all requirements met?

    • [ ] Code completed
    • [ ] Smoke tested
    • [ ] Unit tests added
    • [ ] Code documentation added
    • [ ] Any pending items have an associated Issue

    Complete description

    How did you fix the bug, make the feature etc. Link to any design docs etc

    Tracking Issue

    https://github.com/lyft/flyte/issues/

    Follow-up issue

    NA OR https://github.com/lyft/flyte/issues/

    opened by evalsocket 9
  • Feature/goreleaser

    Feature/goreleaser

    TL;DR

    Added change for publishing flytectl binary in brew and scoop

    Type

    • [ ] Bug Fix
    • [x] Feature
    • [ ] Plugin

    Are all requirements met?

    • [ ] Code completed
    • [ ] Smoke tested
    • [ ] Unit tests added
    • [ ] Code documentation added
    • [ ] Any pending items have an associated Issue

    Complete description

    • Added goreleaser change for brew and scoop
    • Added workflow for goreleaser
    • Added install.sh script for darwin and Linux
    opened by evalsocket 8
  • [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    This PR was automatically created by Snyk using the credentials of a real user.


    Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

    Changes included in this PR

    • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
      • doc-requirements.txt

    Vulnerabilities that will be fixed

    By pinning:

    Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- medium severity | 551/1000
    Why? Recently disclosed, Has a fix available, CVSS 5.3 | Regular Expression Denial of Service (ReDoS)
    SNYK-PYTHON-SETUPTOOLS-3180412 | setuptools:
    39.0.1 -> 65.5.1
    | No | No Known Exploit

    (*) Note that the real score may have changed since the PR was raised.

    Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

    Check the changes in this PR to ensure they won't cause issues with your project.


    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: ๐Ÿง View latest project report

    ๐Ÿ›  Adjust project settings

    ๐Ÿ“š Read more about Snyk's upgrade and patch logic


    Learn how to fix vulnerabilities with free interactive lessons:

    ๐Ÿฆ‰ Regular Expression Denial of Service (ReDoS)

    opened by eapolinario 1
  • Bump certifi from 2021.10.8 to 2022.12.7

    Bump certifi from 2021.10.8 to 2022.12.7

    Bumps certifi from 2021.10.8 to 2022.12.7.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies python 
    opened by dependabot[bot] 1
  • [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    This PR was automatically created by Snyk using the credentials of a real user.


    Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

    Changes included in this PR

    • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
      • doc-requirements.txt

    Vulnerabilities that will be fixed

    By pinning:

    Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- low severity | 441/1000
    Why? Recently disclosed, Has a fix available, CVSS 3.1 | Regular Expression Denial of Service (ReDoS)
    SNYK-PYTHON-SETUPTOOLS-3113904 | setuptools:
    39.0.1 -> 65.5.1
    | No | No Known Exploit

    (*) Note that the real score may have changed since the PR was raised.

    Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

    Check the changes in this PR to ensure they won't cause issues with your project.


    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: ๐Ÿง View latest project report

    ๐Ÿ›  Adjust project settings

    ๐Ÿ“š Read more about Snyk's upgrade and patch logic


    Learn how to fix vulnerabilities with free interactive lessons:

    ๐Ÿฆ‰ Regular Expression Denial of Service (ReDoS)

    opened by EngHabu 1
  • [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    This PR was automatically created by Snyk using the credentials of a real user.


    Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

    Changes included in this PR

    • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
      • doc-requirements.txt

    Vulnerabilities that will be fixed

    By pinning:

    Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- low severity | 441/1000
    Why? Recently disclosed, Has a fix available, CVSS 3.1 | Regular Expression Denial of Service (ReDoS)
    SNYK-PYTHON-SETUPTOOLS-3113904 | setuptools:
    39.0.1 -> 65.5.1
    | No | No Known Exploit

    (*) Note that the real score may have changed since the PR was raised.

    Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

    Check the changes in this PR to ensure they won't cause issues with your project.


    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: ๐Ÿง View latest project report

    ๐Ÿ›  Adjust project settings

    ๐Ÿ“š Read more about Snyk's upgrade and patch logic


    Learn how to fix vulnerabilities with free interactive lessons:

    ๐Ÿฆ‰ Regular Expression Denial of Service (ReDoS)

    opened by EngHabu 1
  • [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

    Changes included in this PR

    • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
      • doc-requirements.txt

    Vulnerabilities that will be fixed

    By pinning:

    Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- low severity | 441/1000
    Why? Recently disclosed, Has a fix available, CVSS 3.1 | Regular Expression Denial of Service (ReDoS)
    SNYK-PYTHON-SETUPTOOLS-3113904 | setuptools:
    39.0.1 -> 65.5.1
    | No | No Known Exploit

    (*) Note that the real score may have changed since the PR was raised.

    Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

    Check the changes in this PR to ensure they won't cause issues with your project.


    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: ๐Ÿง View latest project report

    ๐Ÿ›  Adjust project settings

    ๐Ÿ“š Read more about Snyk's upgrade and patch logic


    Learn how to fix vulnerabilities with free interactive lessons:

    ๐Ÿฆ‰ Regular Expression Denial of Service (ReDoS)

    opened by snyk-bot 0
  • [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    [Snyk] Security upgrade setuptools from 39.0.1 to 65.5.1

    This PR was automatically created by Snyk using the credentials of a real user.


    Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

    Changes included in this PR

    • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
      • doc-requirements.txt

    Vulnerabilities that will be fixed

    By pinning:

    Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- low severity | 441/1000
    Why? Recently disclosed, Has a fix available, CVSS 3.1 | Regular Expression Denial of Service (ReDoS)
    SNYK-PYTHON-SETUPTOOLS-3113904 | setuptools:
    39.0.1 -> 65.5.1
    | No | No Known Exploit

    (*) Note that the real score may have changed since the PR was raised.

    Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

    Check the changes in this PR to ensure they won't cause issues with your project.


    Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

    For more information: ๐Ÿง View latest project report

    ๐Ÿ›  Adjust project settings

    ๐Ÿ“š Read more about Snyk's upgrade and patch logic


    Learn how to fix vulnerabilities with free interactive lessons:

    ๐Ÿฆ‰ Regular Expression Denial of Service (ReDoS)

    opened by EngHabu 1
Releases(v0.6.25)
Owner
Flyte
Organization that hosts the Flyte Project with all of the core components. Flyte is an LF AI & Data Incubating project
Flyte
Mutagen Compose is a modified version of Docker Compose that offers automated integration with Mutagen.

Mutagen Compose Mutagen Compose is a (minimally) modified version of Docker Compose that offers automated integration with Mutagen. This allows you to

Mutagen 81 Dec 22, 2022
Fast cross-platform HTTP benchmarking tool written in Go

bombardier bombardier is a HTTP(S) benchmarking tool. It is written in Go programming language and uses excellent fasthttp instead of Go's default htt

ะœะฐะบัะธะผ ะคะตะดะพัะตะตะฒ 3.9k Jan 2, 2023
:rocket: Modern cross-platform HTTP load-testing tool written in Go

English | ไธญๆ–‡ Cassowary is a modern HTTP/S, intuitive & cross-platform load testing tool built in Go for developers, testers and sysadmins. Cassowary d

Roger Welin 643 Dec 29, 2022
Triggers an update to a Koyeb app service to re-deploy the latest docker image

Triggers an update to a Koyeb app service to re-deploy the latest docker image

Reece May 3 May 5, 2021
Latest block exporter to monitor your own nodes !

Ethereum Block Prometheus Exporter Deeply copied from 31z4/ethereum-prometheus-exporter Thanks a lot for his work ! This service exports the latest bl

iderr 0 Nov 5, 2021
Terraform Provider for Latest HashiCorp Product Versions

terraform-provider-hashicorpversions The purpose of this Terraform provider is to get the latest semantic version of any of the suite of HashiCorp too

Justin DeFrank 3 May 16, 2022
Cross-platform beanstalkd queue server admin console.

Overview aurora is a web-based Beanstalkd queue server console written in Go and works on macOS, Linux, and Windows machines. The main idea behind usi

null 571 Dec 30, 2022
Based on the electron Cross-platform Mini browser

Based on the electron Cross-platform Mini browser

ๆฑ ่พนๆ ‘ไธ‹ 1 May 1, 2022
Defalyzer: A cross-platform software that focuses on defacement analyzing and mirror tracking

Project Defalyzer is a cross-platform software that focuses on defacement analyz

numaN 13 Jul 26, 2022
This plugin helps you to use the AWS Command Line Interface (AWS CLI) to start and end sessions to your managed instances

Session Manager Plugin This plugin helps you to use the AWS Command Line Interface (AWS CLI) to start and end sessions to your managed instances. Sess

Amazon Web Services 180 Dec 28, 2022
The Coherence command line interface (CLI) is a lightweight tool, in the tradition of tools such as kubectl

Coherence Command Line Interface (CLI) Contents Overview Why use the Coherence C

Oracle 12 Dec 15, 2022
Prevent Kubernetes misconfigurations from ever making it (again ๐Ÿ˜ค) to production! The CLI integration provides policy enforcement solution to run automatic checks for rule violations. Docs: https://hub.datree.io

What is Datree? Datree helps to prevent Kubernetes misconfigurations from ever making it to production. The CLI integration can be used locally or in

datree.io 6.1k Jan 1, 2023
Alertmanager-cli is a cli writtin in golang to silence alerts in AlertManager

Alertmanager-cli is a cli writtin in golang to silence alerts in AlertManager

Snigdha Sambit Aryakumar 4 Aug 27, 2022
Build Go Toolchains /w native libs for cross-compilation

gonative Cross compiled Go binaries are not suitable for production applications because code in the standard library relies on Cgo for DNS resolution

Alan Shreve 336 Dec 20, 2022
A dead simple, no frills Go cross compile tool

Gox - Simple Go Cross Compilation Gox is a simple, no-frills tool for Go cross compilation that behaves a lot like standard go build. Gox will paralle

Mitchell Hashimoto 4.4k Jan 1, 2023
a build tool for Go, with a focus on cross-compiling, packaging and deployment

goxc NOTE: goxc has long been in maintenance mode. Ever since Go1.5 supported simple cross-compilation, this tool lost much of its value. There are st

Am Laher 1.7k Dec 9, 2022
A cross-language distributed transaction manager

English Docs ่ทจ่ฏญ่จ€ๅˆ†ๅธƒๅผไบ‹ๅŠก็ฎก็†ๅ™จ DTMๆ˜ฏไธ€ๆฌพgolangๅผ€ๅ‘็š„ๅˆ†ๅธƒๅผไบ‹ๅŠก็ฎก็†ๅ™จ๏ผŒ่งฃๅ†ณไบ†่ทจๆ•ฐๆฎๅบ“ใ€่ทจๆœๅŠกใ€่ทจ่ฏญ่จ€ๆ ˆๆ›ดๆ–ฐๆ•ฐๆฎ็š„ไธ€่‡ดๆ€ง้—ฎ้ข˜ใ€‚ ไป–ไผ˜้›…

DTM Development and Communities 8.1k Dec 31, 2022
Quickly cross-compile your C code

WORK IN PROGRESS: Viceroy is a very early work in progress and is subject to breaking changes. It's also subject to not really working all that well y

Robert Fratto 10 Aug 19, 2022