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:

93,850

Downloads of v 1.3.0:

169

Last Update:

06 Jul 2018

Package Maintainer(s):

Software Author(s):

  • Project Kudu contributors

Tags:

azure rest api

ARMClient

Downloads:

93,850

Downloads of v 1.3.0:

169

Maintainer(s):

Software Author(s):

  • Project Kudu contributors

Tags:

azure rest api

ARMClient

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Failed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
WARNING

This package was rejected on 05 Jan 2019. The reviewer chocolatey-ops has listed the following reason(s):

davidebbo (maintainer) on 06 Jul 2018 13:23:34 +00:00:

User 'davidebbo' (maintainer) submitted package.

chocolatey-ops (reviewer) on 06 Jul 2018 13:57:14 +00:00:

ARMClient has failed automated validation.

Requirements

Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • Binary files (.exe, .msi, .zip, etc) have been included without including a LICENSE.txt file. This file is required when including binaries More...
  • Binary files (.exe, .msi, .zip) have been included without including a VERIFICATION.txt file. This file is required when including binaries More...
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...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Title (title) matches id exactly. Please consider using something slightly more descriptive for the title in the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source
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 package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...
  • Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

chocolatey-ops (reviewer) on 06 Jul 2018 19:08:59 +00:00:

ARMClient has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/f9eadf91c8ac857efa82cecf676dd322 for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 21 Dec 2018 10:32:02 +00:00:

We've found ARMClient v1.3.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.

chocolatey-ops (reviewer) on 05 Jan 2019 10:32:28 +00:00:

Unfortunately there has not been progress to move ARMClient v1.3.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

A simple command line tool to invoke the Azure Resource Manager API


tools\AADClient.exe
md5: 8325CA94A4FFE4644E4055F87D241F53 | sha1: 591CE9E9389016A554115C9CFC083FDA685B4EE8 | sha256: 5A482E1D853AAA7A993F7F510130527812228D7A643C570A53DF8FA4C8F3A0DD | sha512: B1A4239C5AB0C31D9BE4B5F6697A50A49091748E02FAD81C28AB5D44C2484C76810EEB13B907183E2ECE286D48BF821B205058C37B3AA64BC8F5EDE18A924BBA
tools\ARMClient.Authentication.dll
md5: D3FB564AF70B0EDF5EA5DB935B060B33 | sha1: 23F1FACA584D4FBC40379AD42D1CA3F9D1BFAC23 | sha256: CDC84A0B1C67332366CB819E7B266BD791380CC57C75CF6AADC1148C15141D8E | sha512: 5C900DFA785B0FB482764709315778303CCB1D5361F97144A66E0883019E4984AA544B1A77D6A464776C1B45E9E16F11231748C466FF03C7059C468F63D8B29A
tools\ARMClient.exe
md5: BEEAC8206B2BD915A3AED70DC3FACEE7 | sha1: C2DF4DBDB0C620BB91D6A553060A0780272A22D1 | sha256: 9BA8866746EFF08FC86B30B989D07A8E69CE45B4F2A519E88419C284C4B5832C | sha512: 6912A07164CA124BCF50A80A4C43C8A9CCEBBE9F7DA6DFBE9AE945C576F4B000AEB045ED54B1421056FCE648C8BAB7CE179D1664990BF1315804C117269ABCC1
tools\Microsoft.IdentityModel.Clients.ActiveDirectory.dll
md5: 958F796F41D548A258962522DE95E4AD | sha1: FF2BE4330C9CA5E618F7ACF9CFF37605BD048F46 | sha256: 5744A22C3C7AD04ED696CE06DDC6E74B3A5208C189DEEC8B996AEE3467E746F0 | sha512: 332F8B2CCF7D24EBDD74CEE48CCFCCED243CCABEE28EB097EA111658AD1A7C82C86DEC92EE20E1928BCBCBB431EF90FF0FDED8F6AD30629C410BF76B0FB6A9F7
tools\Microsoft.IdentityModel.Clients.ActiveDirectory.WindowsForms.dll
md5: 332C30DEC059DD527BE5F853F7DF96E9 | sha1: A9515AA0EEF0597D177CB27AF70E6A1C133B2388 | sha256: 6475D7C109D9D4039E9AE9E7E52ADD4C2024730B12ED6FA032414E0131B78FB0 | sha512: EFF07B00F4F3E848218C23E30CBB1E510BE4EE650F1018CF4C3CD16869331A421AE30C3923F18660DAEB3FFD017F46FC904BA8A12485BDF86EC2EA649A8EEEC1
tools\Newtonsoft.Json.dll
md5: 3EAEFE4332269092760BD0C1C966D2C9 | sha1: E6326487B9BB0BCB500A0D04EF09D01806BAB73F | sha256: 77176533046DC76964A8FA184DF90EABB705B6A7B73249CA72CA3F6903A38B34 | sha512: 28C88F277DD92925AD7D347CA8EF18B70E23FB7A40882E76B7215F98ADB65A4F606B162D322B05AE154731B006678DA4CFC3DFEEFFDC8FD1EEE59297E426D965
tools\System.IdentityModel.Tokens.Jwt.dll
md5: 74C4B94F7ED7C0F54FD2B2B3D40DA903 | sha1: 1C7C756EE59820A77287D4086EDDD3784DBEAA44 | sha256: 449B4231DCCBE8D204F587A5192F783761CF7F045F543314E56B40B7CEFE576C | sha512: E4A00B217CA178CC6C801C315D4ABC836F5669EC03BC9525D821526F2B06BE3C8FCFED67030FBCFDCD3CCE2D91B695AF0D3B34964B71A316810E9FB8D2996E7B
tools\System.Net.Http.Formatting.dll
md5: 0FC2047E361B79AC15755B1ED400F819 | sha1: 638F36DCC3A8131B8BEBDFB3A0930A764AA9984B | sha256: 76EA4B2D47BB238C1F2AC0C62F1BE4D34BC71397662E3760EA0C684EC4A429C0 | sha512: 3BE94E64E45B7369C37DE381DEBC6BF19D216E470EC4C01778FA1B8B7AE99E5CD230FE896BDBDC693CF889A744FA1C0234E86052D2FE92E29C73F47D6D8EF57D

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
ARMClient 1.8.0 6794 Friday, May 22, 2020 Approved
ARMClient 1.6.0 47860 Tuesday, April 21, 2020 Approved
ARMClient 1.5.0 1868 Tuesday, February 4, 2020 Approved
ARMClient 1.4.0 2804 Sunday, August 18, 2019 Approved
ARMClient 1.2.0 14950 Friday, December 9, 2016 Approved
ARMClient 1.1.2 709 Saturday, November 19, 2016 Approved
ARMClient 1.1.1 1836 Monday, December 14, 2015 Approved
ARMClient 1.1.0 653 Thursday, October 29, 2015 Approved
ARMClient 1.0.3 575 Tuesday, September 22, 2015 Approved
ARMClient 1.0.1 514 Wednesday, September 9, 2015 Approved
ARMClient 1.0.0 1034 Wednesday, March 4, 2015 Approved
ARMClient 0.9.2 512 Friday, February 27, 2015 Approved
ARMClient 0.9.1 579 Friday, January 16, 2015 Approved
ARMClient 0.9 504 Friday, January 16, 2015 Approved

This package has no dependencies.

Discussion for the ARMClient Package

Ground Rules:

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