Downloads:

3,445

Downloads of v 0.12.19:

33

Last Update:

20 Nov 2020

Package Maintainer(s):

Software Author(s):

  • Alex Ellis

Tags:

faas-cli faas openfaas serverless kubernetes docker swarm functions function faas-netes

Official CLI for OpenFaaS

0.12.19 | Updated: 20 Nov 2020

Downloads:

3,445

Downloads of v 0.12.19:

33

Maintainer(s):

Software Author(s):

  • Alex Ellis

Official CLI for OpenFaaS 0.12.19

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install Official CLI for OpenFaaS, run the following command from the command line or from PowerShell:

>

To upgrade Official CLI for OpenFaaS, run the following command from the command line or from PowerShell:

>

To uninstall Official CLI for OpenFaaS, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade faas-cli -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade faas-cli -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure faas-cli installed
  win_chocolatey:
    name: faas-cli
    state: present
    version: 0.12.19
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'faas-cli' do
  action    :install
  version  '0.12.19'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: faas-cli,
    Version: 0.12.19,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller faas-cli
{
   Name     = 'faas-cli'
   Ensure   = 'Present'
   Version  = '0.12.19'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'faas-cli':
  provider => 'chocolatey',
  ensure   => '0.12.19',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install faas-cli version="0.12.19" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 21 Nov 2020.

Description

faas-cli

Build Status
Go Report Card
License: MIT
OpenFaaS

This is a CLI for use with OpenFaaS - a serverless functions framework for Docker & Kubernetes.

> Before using this tool please setup OpenFaaS by following instructions over on the main repo.

The CLI can be used to build and deploy functions to OpenFaaS. You can build OpenFaaS functions from a set of supported language templates (such as Node.js, Python, CSharp and Ruby). That means you just write a handler file such as (handler.py/handler.js) and the CLI does the rest to create a Docker image.

Demo: ASCII cinema

TL;DR - Introductory tutorial

Blog: Coffee with the FaaS-CLI

Run the CLI

The main commands supported by the CLI are:

  • faas-cli new - creates a new function via a template in the current directory

  • faas-cli login - stores basic auth credentials for OpenFaaS gateway (supports multiple gateways)

  • faas-cli logout - removes basic auth credentials for a given gateway

  • faas-cli up - a combination of build/push and deploy

  • faas-cli build - builds Docker images from the supported language types

  • faas-cli push - pushes Docker images into a registry

  • faas-cli deploy - deploys the functions into a local or remote OpenFaaS gateway

  • faas-cli remove - removes the functions from a local or remote OpenFaaS gateway

  • faas-cli invoke - invokes the functions and reads from STDIN for the body of the request

  • faas-cli store - allows browsing and deploying OpenFaaS store functions

  • faas-cli secret - manage secrets for your functions

  • faas-cli auth - (alpha) initiates an OAuth2 authorization flow to obtain a cookie

FaaS-CLI Developers / Contributors

See contributing guide.

License

This project is part of OpenFaaS and is licensed under the MIT License.


legal\LICENSE.txt
From: https://github.com/openfaas/faas-cli/blob/master/LICENSE

LICENSE

 MIT License

Copyright (c) 2016-2017 Alex Ellis

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
legal\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

1.  Download the installer:

    x32: https://github.com/openfaas/faas-cli/releases/download/0.12.19/faas-cli.exe

2.  You can use one of the following methods to obtain the checksum: 
    - Use powershell function 'Get-FileHash'
    - Use Chocolatey utility 'checksum.exe'
    - Using AU:
        Get-RemoteChecksum https://github.com/openfaas/faas-cli/releases/download/0.12.19/faas-cli.exe

3.  Compare to Checksum:

    checksum_from_file: https://github.com/openfaas/faas-cli/releases/download/0.12.19/faas-cli.exe.sha256

    OR
    
    checksum32: D54AC86C5725236615A59F0D5FA5FF91E2F9B185D5CEF789CEB816440AFB3AFC
tools\faas-cli.exe
md5: 2F191B3E50A38EED21D9BF059747BD14 | sha1: 76055C5F1878BC5FB877655EC8F0956BEADB5A13 | sha256: D54AC86C5725236615A59F0D5FA5FF91E2F9B185D5CEF789CEB816440AFB3AFC | sha512: 9A7AFB8833E1050513B82D374D07A103D0B86898FE0E0C253D0696F229FA3A4E3015C83D46E5C69A10761F5C6B63E6C3E131AB8DAC0273080004E11A98E02AC0

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Official CLI for OpenFaaS 0.12.18 11 Thursday, November 19, 2020 Approved
Official CLI for OpenFaaS 0.12.14 79 Friday, October 9, 2020 Approved
Official CLI for OpenFaaS 0.12.13 70 Thursday, September 17, 2020 Approved
Official CLI for OpenFaaS 0.12.9 78 Tuesday, August 25, 2020 Approved
Official CLI for OpenFaaS 0.12.8 141 Thursday, July 2, 2020 Approved
Official CLI for OpenFaaS 0.12.6 28 Tuesday, June 30, 2020 Approved
Official CLI for OpenFaaS 0.12.4 136 Saturday, May 2, 2020 Approved
Official CLI for OpenFaaS 0.12.3 69 Friday, April 24, 2020 Approved
Official CLI for OpenFaaS 0.12.2 137 Wednesday, March 25, 2020 Approved

This package has no dependencies.

Discussion for the Official CLI for OpenFaaS Package

Ground Rules:

  • This discussion is only about Official CLI for OpenFaaS and the Official CLI for OpenFaaS package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Official CLI for OpenFaaS, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus