Downloads:

1,307

Downloads of v 1.9.0:

75

Last Update:

25 Jan 2019

Package Maintainer(s):

Software Author(s):

  • Weaveworks

Tags:

flux fluxctl weaveworks gitops kubernetes devops cli docker containers

Flux Command Line Interface

This is not the latest version of Flux Command Line Interface available.

1.9.0 | Updated: 25 Jan 2019

Downloads:

1,307

Downloads of v 1.9.0:

75

Maintainer(s):

Software Author(s):

  • Weaveworks

Tags:

flux fluxctl weaveworks gitops kubernetes devops cli docker containers

Flux Command Line Interface 1.9.0

This is not the latest version of Flux Command Line Interface available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install Flux Command Line Interface, run the following command from the command line or from PowerShell:

>

To upgrade Flux Command Line Interface, run the following command from the command line or from PowerShell:

>

To uninstall Flux Command Line Interface, 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 fluxctl -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 fluxctl -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 fluxctl installed
  win_chocolatey:
    name: fluxctl
    state: present
    version: 1.9.0
    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 'fluxctl' do
  action    :install
  version  '1.9.0'
  source   'STEP 3 URL'
end

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


Chocolatey::Ensure-Package
(
    Name: fluxctl,
    Version: 1.9.0,
    Source: STEP 3 URL
);

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


cChocoPackageInstaller fluxctl
{
   Name     = 'fluxctl'
   Ensure   = 'Present'
   Version  = '1.9.0'
   Source   = 'STEP 3 URL'
}

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


package { 'fluxctl':
  provider => 'chocolatey',
  ensure   => '1.9.0',
  source   => 'STEP 3 URL',
}

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


salt '*' chocolatey.install fluxctl version="1.9.0" 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 by moderator gep13 on 29 Jan 2019.

Description

Weaveworks fluxctl

Managing Flux from the Command Line

Flux allows you to declaratively define the deployment state of your Kubernetes environment. Deployements are automated and triggered off of code pushes.
Flux is a tool that automatically ensures that the state of a cluster matches your specified configuration in git. It uses an operator in the cluster to trigger deployments inside Kubernetes, which means you don't need a separate CD tool.
It monitors all relevant image repositories, detects new images, triggers deployments and updates the desired running configuration based on that (and a configurable policy).

Additional Documentation

More information can be found at the official Weavworks site and Flux GitHub repository.
The following links provide additional documentation on GitOps, Flux.

tools\chocolateyinstall.ps1 
$ErrorActionPreference = 'Stop';

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

$packageArgs = @{
    packageName     = $packageName
    fileFullPath    = Join-Path $toolsDir "fluxctl.exe"
    Url             = 'https://github.com/weaveworks/flux/releases/download/1.9.0/fluxctl_windows_amd64'
    checksum        = "9241C754EBCF7B52374EF01AF03D19F0933282051159A785A48AD8EB01E05B79"
    checksumType    = "SHA256"    
}

#Download the file from releases
Get-ChocolateyWebFile @packageArgs

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
Flux Command Line Interface 1.17.0 176 Tuesday, January 7, 2020 Approved
Flux Command Line Interface 1.16.0 53 Thursday, December 5, 2019 Approved
Flux Command Line Interface 1.15.0 146 Wednesday, October 9, 2019 Approved
Flux Command Line Interface 1.14.2 77 Thursday, September 12, 2019 Approved
Flux Command Line Interface 1.13.3 93 Tuesday, July 30, 2019 Approved
Flux Command Line Interface 1.13.2 63 Thursday, July 11, 2019 Approved
Flux Command Line Interface 1.13.1 56 Friday, June 28, 2019 Approved
Flux Command Line Interface 1.13.0 32 Wednesday, June 19, 2019 Approved
Flux Command Line Interface 1.12.3 69 Thursday, May 23, 2019 Approved
Flux Command Line Interface 1.12.2 57 Thursday, May 9, 2019 Approved

This package has no dependencies.

Discussion for the Flux Command Line Interface Package

Ground Rules:

  • This discussion is only about Flux Command Line Interface and the Flux Command Line Interface 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 Flux Command Line Interface, 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