Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
465
Downloads of v 1.3.0:
26
Last Update:
02 Mar 2021
Package Maintainer(s):
Software Author(s):
- Flexera
Tags:
fpt flexera rightscale API rest cli go golang- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download

fpt - Flexera Policy Tool
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
465
Downloads of v 1.3.0:
26
Maintainer(s):
Software Author(s):
- Flexera
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
All Checks are Passing
2 Passing Test
To install fpt - Flexera Policy Tool, run the following command from the command line or from PowerShell:
To upgrade fpt - Flexera Policy Tool, run the following command from the command line or from PowerShell:
To uninstall fpt - Flexera Policy Tool, 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
2. Get the package into your environment-
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
-
Open Source
- Download the Package Download
- Follow manual internalization instructions
-
Package Internalizer (C4B)
- Run
choco download fpt --internalize --source=https://community.chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://community.chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade fpt -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 fpt -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 fpt installed
win_chocolatey:
name: fpt
state: present
version: 1.3.0
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'fpt' do
action :install
version '1.3.0'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: fpt,
Version: 1.3.0,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller fpt
{
Name = 'fpt'
Ensure = 'Present'
Version = '1.3.0'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'fpt':
provider => 'chocolatey',
ensure => '1.3.0',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install fpt version="1.3.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 as a trusted package on 02 Mar 2021.
fpt - Flexera Policy Tool
fpt
is a command line tool to aid in the development and testing of RightScale Policies. The tool is able to syntax check, upload, and run Policies.
Configuration
fpt
interfaces with the Policy API. Credentials for the API can be provided in two ways:
- YAML-based configuration file - Run
fpt config account <name>
, where name is a nickname for the account, to interactively write the configuration file into$HOME/.fpt.yml
for the first time. You will be prompted for the following fields:- Account ID - Numeric account number, such as
60073
- API endpoint host - Hostname, typically
governance-3.rightscale.com
- Refresh Token - Your personal OAuth token available from Settings > Account Settings > API Credentials in the RightScale Cloud Management dashboard
- Account ID - Numeric account number, such as
- Environment variables - These are meant to be used by build systems such as Travis CI. The following vars must be set:
FPT_LOGIN_ACCOUNT_ID
,FPT_LOGIN_ACCOUNT_HOST
,FPT_LOGIN_ACCOUNT_REFRESH_TOKEN
. These variables are equivalent to the ones described in the YAML section above.
Please Note: This is an automatically updated package. If you find it is
out of date by more than a day or two, please contact the maintainer(s) and
let them know the package is no longer updating correctly.
$ErrorActionPreference = 'Stop';
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$packageArgs = @{
packageName = $env:ChocolateyPackageName
unzipLocation = $toolsDir
url64bit = 'https://binaries.rightscale.com/rsbin/fpt/v1.3.0/fpt-windows-amd64.zip'
checksum64 = 'cb360d26169529a338f28d5cb0cb4af3dbe512cb010fcae9681c28d2eab88630'
checksumType64 = 'sha256'
}
Install-ChocolateyZipPackage @packageArgs
Log in or click on link to see number of positives.
- fpt.1.3.0.nupkg (da6b29db42d4) - ## / 63
- fpt-windows-amd64.zip (cb360d261695) - ## / 64
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 |
---|---|---|---|
fpt - Flexera Policy Tool 1.3.0 | 26 | Tuesday, March 2, 2021 | Approved |
fpt - Flexera Policy Tool 1.2.2 | 29 | Saturday, January 16, 2021 | Approved |
fpt - Flexera Policy Tool 1.2.1 | 24 | Friday, December 11, 2020 | Approved |
fpt - Flexera Policy Tool 1.2.0 | 30 | Thursday, October 22, 2020 | Approved |
fpt - Flexera Policy Tool 1.1.4 | 83 | Wednesday, July 1, 2020 | Approved |
fpt - Flexera Policy Tool 1.1.3 | 32 | Friday, June 26, 2020 | Approved |
fpt - Flexera Policy Tool 1.1.2 | 51 | Thursday, May 21, 2020 | Approved |
fpt - Flexera Policy Tool 1.1.1 | 34 | Thursday, May 21, 2020 | Approved |
fpt - Flexera Policy Tool 1.1.0 | 39 | Wednesday, May 6, 2020 | Approved |
fpt - Flexera Policy Tool 1.0.9 | 59 | Thursday, March 12, 2020 | Approved |
fpt - Flexera Policy Tool 1.0.8 | 58 | Saturday, February 29, 2020 | Approved |
See the ChangeLog.
This package has no dependencies.
Ground Rules:
- This discussion is only about fpt - Flexera Policy Tool and the fpt - Flexera Policy Tool 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 fpt - Flexera Policy Tool, 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.