Checklist
Is Your Feature Request Related To A Problem? Please describe.
In the current version of Chocolatey CLI, 2.6.0, when the useRememberedArgumentsForUpgrades feature is enabled, if you install a package using command line arguments, those command line arguments (if they are part of the collection of arguments that are allowed) are saved within a .arguments file, and then when the package is upgraded, these arguments are hydrated from the .arguments file, so that they don't need to be set at the command line each time a package is upgraded.
Currently, it is possible to "see" what command line arguments have been persisted for a given package, by using the choco info command, for example
choco info chocolatey-agent --local-only
which will show:
However, this is the only management of these arguments that can be done.
If you wanted to remove these arguments, so that they are not applied during the next upgrade, you would have to go into the .chocolatey folder, and find the .arguments file for the package you want to upgrade, and then delete the .arguments file.
This isn't ideal, as it relies on the end user having knowledge outwith the day to day running of Chocolatey CLI.
Describe The Solution. Why is it needed?
The solution here would be to introduce another Chocolatey CLI command to allow the full management of remembered arguments for a package. This would include the sub-commands:
With this in place, the end user could then choose to:
- "see" the remembered arguments for a package
- reset the remembered arguments, without the need to go hunting for a
.arguments file
- augment the remembered arguments, by adding additional arguments for the next upgrade
Due to the fact that the remembered arguments are encrypted within the .arguments file, it is not possible to manaully augment the arguments that have been saved for a given package.
The suggested command name for this functionailty would be choco arguments, but open to other suggestions here.
Additional Context
The need for this feature came out of a discussion that was had internally on this issue, please refer to that for any additional context that might be required.
Acceptance Criteria
- User is able to show the remembered arguments for a package using the
list sub-command
- User is able to reset the remembered arguments for a package using the
unset sub-command
- User is able to add/modify the remembered arguments for a package using the
set sub-command
- User is not able to change remembered arguments for anything other than the latest package version
- User no longer sees the remembered arguments when running the
choco info command
- User is able to use the
-r command line option to get a machine readable version of the remembered arguments
Related Issues
No response
┆Issue is synchronized with this Clickup task by Unito
Checklist
Is Your Feature Request Related To A Problem? Please describe.
In the current version of Chocolatey CLI, 2.6.0, when the useRememberedArgumentsForUpgrades feature is enabled, if you install a package using command line arguments, those command line arguments (if they are part of the collection of arguments that are allowed) are saved within a
.argumentsfile, and then when the package is upgraded, these arguments are hydrated from the.argumentsfile, so that they don't need to be set at the command line each time a package is upgraded.Currently, it is possible to "see" what command line arguments have been persisted for a given package, by using the
choco infocommand, for examplewhich will show:
However, this is the only management of these arguments that can be done.
If you wanted to remove these arguments, so that they are not applied during the next upgrade, you would have to go into the
.chocolateyfolder, and find the.argumentsfile for the package you want to upgrade, and then delete the.argumentsfile.This isn't ideal, as it relies on the end user having knowledge outwith the day to day running of Chocolatey CLI.
Describe The Solution. Why is it needed?
The solution here would be to introduce another Chocolatey CLI command to allow the full management of remembered arguments for a package. This would include the sub-commands:
With this in place, the end user could then choose to:
.argumentsfileDue to the fact that the remembered arguments are encrypted within the
.argumentsfile, it is not possible to manaully augment the arguments that have been saved for a given package.The suggested command name for this functionailty would be
choco arguments, but open to other suggestions here.Additional Context
The need for this feature came out of a discussion that was had internally on this issue, please refer to that for any additional context that might be required.
Acceptance Criteria
listsub-commandunsetsub-commandsetsub-commandchoco infocommand-rcommand line option to get a machine readable version of the remembered argumentsRelated Issues
No response
┆Issue is synchronized with this Clickup task by Unito