Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

63

Downloads of v 1.1.0:

55

Last Update:

09 Dec 2024

Published Date:

09 Dec 2024

Reviewed Date:

14 Nov 2024

Reviewer:

gravatar

Package Maintainer(s):

Software Author(s):

  • VMware VCF

Tags:

vcf cli kubernetes

VCF CLI

(Maintainer responded, waiting for review/Maintainer update)

  • 1
  • 2
  • 3

1.1.0 | Updated: 09 Dec 2024

Downloads:

63

Downloads of v 1.1.0:

55

Published:

09 Dec 2024

Reviewed:

14 Nov 2024

Reviewer:

gravatar

Maintainer(s):

Software Author(s):

  • VMware VCF

VCF CLI 1.1.0

(Maintainer responded, waiting for review/Maintainer update)

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by VMware VCF. The inclusion of VMware VCF trademark(s), if any, upon this webpage is solely to identify VMware VCF goods or services and not for commercial purposes.

  • 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
IMPORTANT

This version is in moderation and has not yet been approved. This means it doesn't show up under normal search.

  • Until approved, you should consider this package version unsafe - it could do very bad things to your system (it probably doesn't but you have been warned, that's why we have moderation).
  • This package version can change wildly over the course of moderation until it is approved. If you install it and it later has changes to this version, you will be out of sync with any changes that have been made to the package. Until approved, you should consider that this package version doesn't even exist.
  • You cannot install this package under normal scenarios. See How to install package version under moderation for more information.
  • There are also no guarantees that it will be approved.
WARNING

There are versions of this package awaiting moderation (possibly just this one). See the Version History section below.

lakshmi.prasad (maintainer) on 07 Oct 2024 13:17:19 +00:00:

User 'lakshmi.prasad' (maintainer) submitted package.

chocolatey-ops (reviewer) on 07 Oct 2024 13:50:49 +00:00:

vcf-cli has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the ReleaseNotes element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The DocsUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The BugTrackerUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The PackageSourceUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The LicenseUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The ProjectUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...

chocolatey-ops (reviewer) on 07 Oct 2024 14:42:53 +00:00:

vcf-cli has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/731f2fc6ae48d7bf7d882afd9b314e18 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

lakshmi.prasad (maintainer) on 07 Oct 2024 16:25:31 +00:00:

User 'lakshmi.prasad' (maintainer) submitted package.

chocolatey-ops (reviewer) on 07 Oct 2024 16:58:28 +00:00:

vcf-cli has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the ReleaseNotes element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The DocsUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The BugTrackerUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The PackageSourceUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The LicenseUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The ProjectUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...

chocolatey-ops (reviewer) on 07 Oct 2024 19:34:54 +00:00:

vcf-cli has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/dc63d5b97740dd7ca685830fe3c57566 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

lakshmi.prasad (maintainer) on 08 Oct 2024 17:04:45 +00:00:

User 'lakshmi.prasad' (maintainer) submitted package.

lakshmi.prasad (maintainer) on 08 Oct 2024 17:19:29 +00:00:

User 'lakshmi.prasad' (maintainer) submitted package.

chocolatey-ops (reviewer) on 08 Oct 2024 17:51:04 +00:00:

vcf-cli has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • In the ReleaseNotes element of the nuspec file a potentially invalid Url has been found. Recommendation is to fix this URL More...
  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
Notes

Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.

  • The DocsUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The BugTrackerUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The PackageSourceUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The LicenseUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The ProjectUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...
  • The ProjectSourceUrl element in the nuspec file should be a valid Url. The reviewer will ensure the specified Url is valid. More...

chocolatey-ops (reviewer) on 08 Oct 2024 18:09:17 +00:00:

vcf-cli has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/60cb652c202cf3d451938f9686983283 for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 08 Oct 2024 18:35:32 +00:00:

vcf-cli has passed automated virus scanning.

lakshmi.prasad (maintainer) on 11 Oct 2024 01:58:04 +00:00:

User 'lakshmi.prasad' (maintainer) submitted package.

chocolatey-ops (reviewer) on 11 Oct 2024 02:32:52 +00:00:

vcf-cli has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...

lakshmi.prasad (maintainer) on 11 Oct 2024 02:49:44 +00:00:

User 'lakshmi.prasad' (maintainer) submitted package.

chocolatey-ops (reviewer) on 11 Oct 2024 03:24:11 +00:00:

vcf-cli has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...

chocolatey-ops (reviewer) on 11 Oct 2024 05:04:55 +00:00:

vcf-cli has failed automated package testing (verification).
Please visit https://gist.github.com/choco-bot/073194cb596717d057c1f2e42fd70f30 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey-community/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

lakshmi.prasad (maintainer) on 11 Oct 2024 05:41:09 +00:00:

This is the error which is causing the above mentioned failure.

2024-10-11 05:04:53,453 5812 [ERROR] - vcf-cli not installed. An error occurred during installation:
Error downloading 'vcf-cli.1.1.0' from 'https://community.chocolatey.org/api/v2/package/vcf-cli/1.1.0'.

But, when attempted download, I didn't find any failures and I could see its getting downloaded as expected.

Also, I've attempted installation and for me its working. Please check the install trace.

C:\WINDOWS\system32> choco install vcf-cli --version=1.1.0 --ignore-http-cache
Chocolatey v2.3.0
Installing the following packages:
vcf-cli
By installing, you accept licenses for the packages.
Downloading package from source 'https://community.chocolatey.org/api/v2/'
Progress: Downloading vcf-cli 1.1.0... 100%

vcf-cli v1.1.0 - Possibly broken
vcf-cli package files install completed. Performing other installation steps.
The package vcf-cli wants to run 'chocolateyInstall.ps1'.
Note: If you don't run this script, the installation will fail.
Note: To confirm automatically next time, use '-y' or consider:
choco feature enable -n allowGlobalConfirmation
Do you want to run the script?([Y]es/[A]ll - yes to all/[N]o/[P]rint): Y

C:\ProgramData\chocolatey\lib\vcf-cli\scripts\v1.1.0
File appears to be downloaded already. Verifying with package checksum to determine if it needs to be redownloaded.
Hashes match.
Hashes match.
Extracting C:\Users\QE\AppData\Local\Temp\chocolatey\vcf-cli\1.1.0\vcf-cli.zip to C:\ProgramData\chocolatey\lib\vcf-cli\scripts\v1.1.0...
C:\ProgramData\chocolatey\lib\vcf-cli\scripts\v1.1.0
WARNING: Unable to setup shell completion for future sessions for the VCF CLI because C:\Users\QE\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 does not exist.
WARNING: Please follow the instructions of 'vcf completion -h' to know how to enable shell completion.
The install of vcf-cli was successful.
Deployed to 'C:\ProgramData\chocolatey\lib\vcf-cli\scripts\v1.1.0'

Chocolatey installed 1/1 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

lakshmi.prasad (maintainer) on 11 Oct 2024 06:04:34 +00:00:

User 'lakshmi.prasad' (maintainer) submitted package.

chocolatey-ops (reviewer) on 11 Oct 2024 06:36:42 +00:00:

vcf-cli has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...

chocolatey-ops (reviewer) on 11 Oct 2024 06:49:26 +00:00:

vcf-cli has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/2046a79b8ff9adf26f501280d71931a3 for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 11 Oct 2024 07:21:34 +00:00:

vcf-cli has passed automated virus scanning.

lakshmi.prasad (maintainer) on 21 Oct 2024 15:04:47 +00:00:

Hello,

Can I get an update on review?

lakshmi.prasad (maintainer) on 21 Oct 2024 15:45:42 +00:00:

Hello,

Can I get an update on review?

lakshmi.prasad (maintainer) on 23 Oct 2024 07:49:30 +00:00:

Hello,

Can I get an update on review?

flcdrg (reviewer) on 14 Nov 2024 09:46:24 +00:00:

The install script include "Broadcom Confidential" in the comments. Either the script is confidential, in which case you probably shouldn't publish it to Chocolatey, or it isn't confidential and you should remove that text.

David

chocolatey-ops (reviewer) on 04 Dec 2024 09:51:15 +00:00:

We've found vcf-cli v1.1.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

lakshmi.prasad (maintainer) on 09 Dec 2024 07:06:49 +00:00:

User 'lakshmi.prasad' (maintainer) submitted package.

lakshmi.prasad (maintainer) on 09 Dec 2024 07:07:57 +00:00:

Hello,

I've updated my package with a new header removing all references to 'Broadcom' confidential. Please check and approve.

Thanks,

chocolatey-ops (reviewer) on 09 Dec 2024 07:39:19 +00:00:

vcf-cli has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...

chocolatey-ops (reviewer) on 09 Dec 2024 07:44:08 +00:00:

vcf-cli has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/76181077fd3401567bb5142dcb687583 for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 09 Dec 2024 07:58:26 +00:00:

vcf-cli has passed automated virus scanning.

Description

The VCF CLI provides integrated and unified command-line access to a broad array of products and solutions in the VMware by Broadcom portfolio. The CLI is based on a plugin architecture where CLI command functionality can be delivered through independently developed plugin binaries


scripts\chocolateyInstall.ps1
# Copyright (c) 2020-2024 Broadcom. All Rights Reserved.
# The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.
# All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

$ErrorActionPreference = 'Stop';
$releaseVersion = 'v1.1.0'
$packageName = 'vcf-cli'
$packagePath = "${releaseVersion}"
$scriptsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$checksumType64 = 'sha256'
$cliExeName = ''
$unzipDirectory = "$scriptsDir\$packagePath"

# Check if we are dealing with an ARM64 architecture
$os = Get-WmiObject -Class Win32_OperatingSystem

New-Item -ItemType Directory -Force -Path $unzipDirectory

if ($os.OSArchitecture -like "*ARM*") {
    $url64 = "https://packages.broadcom.com/artifactory/vcf-distro/vcf-cli/windows/arm64/${releaseVersion}/vcf-cli.zip"
    $checksum64 = '402439ead43e7f67c9742fb50e68bfcb69543d4eee226349a33ac216b7564d82'
    $cliExeName = 'vcf-cli-windows_arm64.exe'
} else {
    $url64 = "https://packages.broadcom.com/artifactory/vcf-distro/vcf-cli/windows/amd64/${releaseVersion}/vcf-cli.zip"
    $checksum64 = '7c02982b6170ae342f196ddefcb4093a81ffb8672e5e04342339415ad270d25e'
    $cliExeName = 'vcf-cli-windows_amd64.exe'
}

$packageArgs = @{
    packageName    = $packageName
    unzipLocation  = $unzipDirectory
    url64bit       = $url64

    softwareName   = 'vcf-cli'

    checksum64     = $checksum64
    checksumType64 = $checksumType64
}

function Install-VCFEnvironment {
    # The default shim normally created by Chocolatey in the bin directory does not forward interrupts to the CLI
    # Since the CLI needs to catch interrupts we prevent chocolatey from creating the shim, and instead
    # we copy the full CLI binary to the bin directory

    $binDirectory = Join-Path $env:ChocolateyInstall 'bin'
    $cliExePath = Join-Path $(Join-Path ${scriptsDir} ${packagePath}) $cliExeName

    $cliExe = Join-Path ${binDirectory} vcf.exe

    Copy-Item "${cliExePath}" "${cliExe}"

    #Create .ignore file so chocolatey does not shim the Exe
    New-Item "${cliExePath}.ignore" -type file -force | Out-Null

    # Setup shell completion
    if (Test-Path -Path $PROFILE) {
        if (-not (Select-String -Path $PROFILE -Pattern "vcf completion powershell" -Quiet)) {
            Add-Content $PROFILE ""
            Add-Content $PROFILE "# VCF shell completion"
            Add-Content $PROFILE "if (Get-Command 'vcf' -ErrorAction SilentlyContinue) {"
            Add-Content $PROFILE "   vcf completion powershell | Out-String | Invoke-Expression"
            Add-Content $PROFILE "}"

            Write-Host -ForegroundColor Green "Enabled shell completion for 'vcf' in $PROFILE."
            Write-Host -ForegroundColor Green "You will need to restart your shell for this to take effect."
        }
    } else {
        Write-Warning "Unable to setup shell completion for future sessions for the VCF CLI because $PROFILE does not exist."
        Write-Warning "Please follow the instructions of 'vcf completion -h' to know how to enable shell completion."
    }
}

# this is a built-in function, read https://docs.chocolatey.org/en-us/create/functions/install-chocolateyzippackage
Install-ChocolateyZipPackage @packageArgs

Install-VCFEnvironment

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.

Add to Builder Version Downloads Last Updated Status
VCF CLI 1.1.0 55 Monday, December 9, 2024
Responded

This package has no dependencies.

Discussion for the VCF CLI Package

Ground Rules:

  • This discussion is only about VCF CLI and the VCF CLI 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 VCF CLI, 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