Downloads:

1,153

Downloads of v 0.7.20:

11

Last Update:

12 May 2021

Package Maintainer(s):

Software Author(s):

  • Civo Ltd

Tags:

civo cli k3s kubernetes control client cluster

civo-cli (Portable)

  • 1
  • 2
  • 3

0.7.20 | Updated: 12 May 2021

Downloads:

1,153

Downloads of v 0.7.20:

11

Maintainer(s):

Software Author(s):

  • Civo Ltd

Tags:

civo cli k3s kubernetes control client cluster

  • 1
  • 2
  • 3
 civo-cli (Portable) 0.7.20

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

To install civo-cli (Portable), run the following command from the command line or from PowerShell:

>

To upgrade civo-cli (Portable), run the following command from the command line or from PowerShell:

>

To uninstall civo-cli (Portable), 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://community.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://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade civo-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 civo-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 civo-cli installed
  win_chocolatey:
    name: civo-cli
    state: present
    version: 0.7.20
    source: STEP 3 URL

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


chocolatey_package 'civo-cli' do
  action    :install
  version  '0.7.20'
  source   'STEP 3 URL'
end

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


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

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


cChocoPackageInstaller civo-cli
{
   Name     = 'civo-cli'
   Ensure   = 'Present'
   Version  = '0.7.20'
   Source   = 'STEP 3 URL'
}

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


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

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


salt '*' chocolatey.install civo-cli version="0.7.20" 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.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 12 May 2021.

Description

civo is a command-line interface for interfacing with the Civo platform.

Civo CLI is a tool to manage your Civo.com account from the terminal. The Civo web control panel has a user-friendly interface for managing your account, but in case you want to automate or run scripts on your account, or have multiple complex services, the command-line interface outlined here will be useful. This guide will cover the set-up and usage of the Civo CLI tool with examples.

NOTE: This package is automatically updated. If it is out of date and there is no newer package submitted, please use the Contact Maintainers functionality to alert me.

tools\chocolateyInstall.ps1 
$ErrorActionPreference = 'Stop'

$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
    packageName    = $env:ChocolateyPackageName
    unzipLocation  = $toolsDir

    url64          = 'https://github.com//civo/cli/releases/download/v0.7.20/civo-0.7.20-windows-amd64.zip'
    checksum64     = '98f70ae3f164d749f97c57d96098fb573441bf5e768bffed83dff3f6c2b79ae5'
    checksumType64 = 'SHA256'
}

Install-ChocolateyZipPackage @packageArgs
tools\chocolateyUninstall.ps1 
  
$ErrorActionPreference = 'Stop';

$civoExe = Get-ChildItem $(Split-Path -Parent $MyInvocation.MyCommand.Definition) | Where-Object -Property Name -Match "civo.exe"

if (-Not($civoExe)) 
{
    Write-Error -Message "civo exe is not found, please contact the maintainer of the package" -Category ResourceUnavailable
}

Write-Host "found civo exe in $($civoExe.FullName)"
Write-Host "attempting to remove it" 

Remove-Item $civoExe.FullName

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
civo-cli (Portable) 0.7.20 11 Wednesday, May 12, 2021 Approved
civo-cli (Portable) 0.7.19 8 Tuesday, May 11, 2021 Approved
civo-cli (Portable) 0.7.18 7 Tuesday, May 11, 2021 Approved
civo-cli (Portable) 0.7.17 7 Tuesday, May 11, 2021 Approved
civo-cli (Portable) 0.7.16 6 Monday, May 10, 2021 Approved
civo-cli (Portable) 0.7.15 7 Saturday, May 8, 2021 Approved
civo-cli (Portable) 0.7.14 10 Thursday, May 6, 2021 Approved
civo-cli (Portable) 0.7.13 15 Monday, April 19, 2021 Approved
civo-cli (Portable) 0.7.12 12 Wednesday, April 14, 2021 Approved
civo-cli (Portable) 0.7.11 9 Wednesday, April 7, 2021 Approved

This package has no dependencies.

Discussion for the civo-cli (Portable) Package

Ground Rules:

  • This discussion is only about civo-cli (Portable) and the civo-cli (Portable) 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 civo-cli (Portable), 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