Ansible
PS DSC
Downloads:
23
Downloads of v 1.1:
23
Last Update:
25 May 2023
Package Maintainer(s):
Software Author(s):
- Martin Brandl
Tags:
- Software Specific:
- Software Site
- Software License
- Software Issues
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
azctx Install
- Software Specific:
- Software Site
- Software License
- Software Issues
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
23
Downloads of v 1.1:
23
Maintainer(s):
Software Author(s):
- Martin Brandl
azctx Install
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Martin Brandl. The inclusion of Martin Brandl trademark(s), if any, upon this webpage is solely to identify Martin Brandl goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
WARNING
This package was rejected on 24 Jul 2023. The reviewer Windos has listed the following reason(s):
Description
azctx helps you switch between azure cli subscriptions back and forth.
Files
tools\azctx_windows_amd64.zip
md5: 8067961E65E7AF3540E4FEB98CC259A6 | sha1: 2176B66FB4E6423460BFB77A2599D059F5AC268F | sha256: C6FCB2F9AD125E53591EE27A9536DF737B4557A60082BE56511B865D88370889 | sha512: 6FBD19575F28DAE4B5D1D0F8B76B9599D69E042D1632EADE1C77ADD3AA5B14AE16D44D398735ED732B074F2101F7EC05CE9C5B96627352EB3EE81E94EF160694
tools\chocolateybeforemodify.ps1
# This runs in 0.9.10+ before upgrade and uninstall.
# Use this file to do things like stop services prior to upgrade or uninstall.
# NOTE: It is an anti-pattern to call chocolateyUninstall.ps1 from here. If you
# need to uninstall an MSI prior to upgrade, put the functionality in this
# file without calling the uninstall script. Make it idempotent in the
# uninstall script so that it doesn't fail when it is already uninstalled.
# NOTE: For upgrades - like the uninstall script, this script always runs from
# the currently installed version, not from the new upgraded package version.
tools\chocolateyinstall.ps1
tools\chocolateyuninstall.ps1
# IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file:
# $f='c:\path\to\thisFile.ps1'
# gc $f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^``]#.*','$1'} | Out-File $f+".~" -en utf8; mv -fo $f+".~" $f
## NOTE: In 80-90% of the cases (95% with licensed versions due to Package Synchronizer and other enhancements),
## AutoUninstaller should be able to detect and handle registry uninstalls without a chocolateyUninstall.ps1.
## See https://docs.chocolatey.org/en-us/choco/commands/uninstall
## and https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateypackage
## If this is an MSI, ensure 'softwareName' is appropriate, then clean up comments and you are done.
## If this is an exe, change fileType, silentArgs, and validExitCodes
$ErrorActionPreference = 'Stop' # stop on all errors
$packageArgs = @{
packageName = $env:ChocolateyPackageName
softwareName = 'azctx*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique
fileType = 'EXE_MSI_OR_MSU' #only one of these: MSI or EXE (ignore MSU for now)
# MSI
silentArgs = "/qn /norestart"
validExitCodes= @(0, 3010, 1605, 1614, 1641) # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
# OTHERS
# Uncomment matching EXE type (sorted by most to least common)
#silentArgs = '/S' # NSIS
#silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup
#silentArgs = '/s' # InstallShield
#silentArgs = '/s /v"/qn"' # InstallShield with MSI
#silentArgs = '/s' # Wise InstallMaster
#silentArgs = '-s' # Squirrel
#silentArgs = '-q' # Install4j
#silentArgs = '-s -u' # Ghost
# Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence.
#silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK)
# https://community.chocolatey.org/packages/autohotkey.portable
#validExitCodes= @(0) #please insert other valid exit codes here
}
# Get-UninstallRegistryKey is new to 0.9.10, if supporting 0.9.9.x and below,
# take a dependency on "chocolatey-core.extension" in your nuspec file.
# This is only a fuzzy search if $softwareName includes '*'. Otherwise it is
# exact. In the case of versions in key names, we recommend removing the version
# and using '*'.
[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName']
if ($key.Count -eq 1) {
$key | % {
$packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below
if ($packageArgs['fileType'] -eq 'MSI') {
# The Product Code GUID is all that should be passed for MSI, and very
# FIRST, because it comes directly after /x, which is already set in the
# Uninstall-ChocolateyPackage msiargs (facepalm).
$packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])"
# Don't pass anything for file, it is ignored for msi (facepalm number 2)
# Alternatively if you need to pass a path to an msi, determine that and
# use it instead of the above in silentArgs, still very first
$packageArgs['file'] = ''
} else {
# NOTES:
# - You probably will need to sanitize $packageArgs['file'] as it comes from the registry and could be in a variety of fun but unusable formats
# - Split args from exe in $packageArgs['file'] and pass those args through $packageArgs['silentArgs'] or ignore them
# - Ensure you don't pass double quotes in $file (aka $packageArgs['file']) - otherwise you will get "Illegal characters in path when you attempt to run this"
# - Review the code for auto-uninstaller for all of the fun things it does in sanitizing - https://github.com/chocolatey/choco/blob/bfe351b7d10c798014efe4bfbb100b171db25099/src/chocolatey/infrastructure.app/services/AutomaticUninstallerService.cs#L142-L192
}
Uninstall-ChocolateyPackage @packageArgs
}
} elseif ($key.Count -eq 0) {
Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
Write-Warning "$($key.Count) matches found!"
Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
Write-Warning "Please alert package maintainer the following keys were matched:"
$key | % {Write-Warning "- $($_.DisplayName)"}
}
## OTHER POWERSHELL FUNCTIONS
## https://docs.chocolatey.org/en-us/create/functions
#Uninstall-ChocolateyZipPackage $packageName # Only necessary if you did not unpack to package directory - see https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateyzippackage
#Uninstall-ChocolateyEnvironmentVariable # 0.9.10+ - https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateyenvironmentvariable
#Uninstall-BinFile # Only needed if you used Install-BinFile - see https://docs.chocolatey.org/en-us/create/functions/uninstall-binfile
## Remove any shortcuts you added in the install script.
tools\LICENSE.txt
MIT License
Copyright (c) 2022 Stefan Kürzeder <[email protected]>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
tools\VERIFICATION.txt
VERIFICATION
azctx_windows_amd64.zip
SHA256 Checksum Value: c6fcb2f9ad125e53591ee27a9536df737b4557a60082be56511b865d88370889
Virus Scan Results
Log in or click on link to see number of positives.
- azxtx.1.1.nupkg (c311728eb9e7) - ## / 64
- azctx_windows_amd64.zip (c6fcb2f9ad12) - ## / 64
- azctx.exe (bc994c180ca9) - ## / 69
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.
Copyright
West Wind Technologies, 2016-2021
Dependencies
This package has no dependencies.
Discussion for the azctx Install Package
Ground Rules:
- This discussion is only about azctx Install and the azctx Install 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 azctx Install, 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.
mjisaak (maintainer) on 24 May 2023 20:19:42 +00:00:
User 'mjisaak' (maintainer) submitted package.
chocolatey-ops (reviewer) on 24 May 2023 20:58:10 +00:00:
azxtx 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.
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...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.
chocolatey-ops (reviewer) on 24 May 2023 21:15:51 +00:00:
azxtx has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/f057bce2696f11d300050e37980f82b2 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 24 May 2023 21:40:36 +00:00:
azxtx has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
gep13 (reviewer) on 25 May 2023 05:12:26 +00:00:
Can you please see the comments in the chocolateyInstall.ps1 file regarding removal of comments:
> # IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file:
> # $f='c:\path\to\thisFile.ps1'
> # gc $f | ? {$_ -notmatch "\s*#"} | % {$_ -replace '(.?)\s?[^``]#.*','$1'} | Out-File $f+"." -en utf8; mv -fo $f+"." $f
Then re-submit the package. Thanks
mjisaak (maintainer) on 25 May 2023 09:30:52 +00:00:
User 'mjisaak' (maintainer) submitted package.
chocolatey-ops (reviewer) on 25 May 2023 10:04:49 +00:00:
azxtx 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.
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...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.
chocolatey-ops (reviewer) on 25 May 2023 10:06:53 +00:00:
azxtx has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/5df2094fbc27750b45b88bd43e3ce23b for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 25 May 2023 10:08:23 +00:00:
azxtx has been flagged as part of automated virus scanning.
Package virus scanning found that at least 1 file within, or downloaded by, the package has between 1 and 5 VirusTotal detections associated with it.
This is not enough detections to prevent the approval of this package version.
gep13 (reviewer) on 25 May 2023 19:04:06 +00:00:
The same comment applied to the uninstall script as well.
Also, since the beforeModify script isn't being used, this can also be removed.
Is there a reason that you are defined
toolsDirbut then not using it, and instead, repeating essentially the same line again?:In all likelihood, since this is a zip package, the uninstall script is not needed at all, and can be removed.
mjisaak (maintainer) on 26 May 2023 07:45:27 +00:00:
Hi gep13,
thank you for the comment.
I have removed the beforeModify and the uninstall script and refactored the install script.
BR
gep13 (reviewer) on 27 May 2023 06:17:19 +00:00:
Can you push the package again? I am not seeing any of the changes that you have made.
mjisaak (maintainer) on 28 May 2023 17:37:14 +00:00:
Hi gep13,
it looks like the push failed. I get an error:
> An error has occurred. It's possible the package version already exists on the repository or a nuspec element is invalid. See error below...
> Chocolatey had an error occur:
> System.InvalidOperationException: Failed to process request. 'Conflict'.
> The remote server returned an error: (409) Conflict.. ---> System.Net.WebException: The remote server returned an error: (409) Conflict.
I just updated the nuspec:
any idea?
gep13 (reviewer) on 30 May 2023 07:25:02 +00:00:
Can you confirm the exact command that you are using to push the package?
mjisaak (maintainer) on 30 May 2023 07:59:32 +00:00:
mjisaak (maintainer) on 30 May 2023 08:22:06 +00:00:
gep13 (reviewer) on 31 May 2023 07:22:33 +00:00:
Can you confirm what version of Chocolatey CLI you are using? The log snippet that you provided doesn't match with the commands that you are running, since you are pushing version 1.1, but the partial log is talking about 1.1.0.
Do you have the package source files stored in a GitHub repository somewhere, if so, what is the address?
mjisaak (maintainer) on 01 Jun 2023 11:16:51 +00:00:
I was using Chocolatey v1.3.1 and just upgraded to Chocolatey v2.0.0
No clue why but choco pack was automatically creating azctx.1.1.0.nupkg (even the version in the nuspec is 1.1).
I was able to upload the package with the new CLI and by using version 1.1.0
The package is not public yet (I will publish it after the package is available). Here is the address:
https://github.com/mjisaak/choco-azctx
gep13 (reviewer) on 05 Jun 2023 06:24:11 +00:00:
In version 2.0.0 of Chocolatey CLI, there was a change in how package version normalization is done. You can read about this here:
https://docs.chocolatey.org/en-us/guides/upgrading-to-chocolatey-v2-v6#package-version-normalization
Let us know when you are ready to continue to the moderation of this package.
mjisaak (maintainer) on 11 Jun 2023 12:25:59 +00:00:
Hi gep13,
thank you, I have pushed the final first version here:
https://community.chocolatey.org/packages/azctx/1.1.0
how can I delete the other version with incorrect name? (https://community.chocolatey.org/packages/azxtx/1.1)
BR,
Martin
Windos (reviewer) on 21 Jul 2023 23:46:58 +00:00:
Just to confirm, this is the version with the incorrect name (azxtx)?
If so, deletion isn't really possibly, but we can go ahead and reject it.
mjisaak (maintainer) on 24 Jul 2023 06:30:55 +00:00:
Hi Windows,
yes, this is the version with the incorrect name - please reject it.
BR,
Martin
Windos (reviewer) on 24 Jul 2023 08:16:11 +00:00:
Status Change - Changed status of package from 'submitted' to 'rejected'.