Imagine you have a connection string variable and you want to update it. You would update the variable and redeploy, however if you made a mistake (edited the wrong variable or the new connection string was not live yet) then you cannot roll back. This is even more of a problem if the variable is sensitive as you can't copy it beforehand.

I would like to be able to version octopus variables, this would include:
- Who
- When
- When deployed
- The ability to roll back/forward.

At the moment we have to source control much of this type work, this obviously negates much of the valuable octopus functionality around environment handling/sensitive variables.

Whenever there is a change in the variable after the creation of the release, we used to get warning saying "Release Snapshot has been changed". But we do have only one option to update the entire release without knowing what has been changed. It would be great if you have any way to find/highlight the variables and their values that will be updated when I click "Update Variables" in the release Snapshot section. It will minimize the risk when it's comes to updating the snapshots for production deployment and it will give a transparent view of what changes are done in the variables post release creation.

I would like to create a step template to run some Postman test suite. For this I thought to pass the test files and environment files to the package. Extract the package somewhere, run powershell in the extracted package and call newman (command line runner for postman).

But I can't add a 'Package variable' to a step template (like for a deployment step.

It would be nice to have this as variable for a step template. In the process, you would then get a dropdown with the available packages, and a dropdown with the possible packagefeeds. The script would then automatically extract the package on the selected deployment target(s), and run powershell inside the context of that package.
This way I could specify relative paths to the files needed as input for the script.

It would be great if Ocotpus could support as an external package feed:

https://inedo.com/support/documentation/upack/tools-and-libraries/upack-cli

This is because using `upack` cross platform cli it is easy to create and publish packages containing applications, to a proget universal format feed. Octopus has an in built zip file feed, but we want to standardise our artifacts feeds to proget as it is purpose built for feed management.

Nuget cli is not good at packaging up for example a single exe to push somewhere - like an apk file - because you first have to generae a nuspec file, and then you have to update that file, and then pack it - this is too much overhead for something that should be trivial, like the zip mechanism.

Hello,

OctoPack / Octo.exe currently does not support the latest nuget XSD spec, and fails to run when newer elements are used in the nuspec:

Repro steps:

1. Create a new nuspec file with all the defaults and inside it add a repository element inside the metadata element. Example:

```xml
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
<metadata>
<repository type="git" url="https://github.com/user/repo&quot; />
</metadata>
</package>
```

2. Run OctoPack or Octo.exe with the pack command, and the following error will be shown:

```
error OCTONUGET: The element 'metadata' in namespace 'http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd'; has invalid child element 'repository' in namespace 'http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd'. List of possible elements expected: 'iconUrl, references, contentFiles, title, summary, description, dependencies, language, releaseNotes, frameworkAssemblies, developmentDependency, packageTypes, licenseUrl, serviceable, tags, copyright' in namespace 'http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd'. This validation error occurred in a 'repository' element.
error OCT-1676060969: There was an error calling NuGet. Please see the output above for more details. Command line: 'T:\agent01\w\e21f69818d8a7e42\packages\OctoPack.3.6.3\build\nuget.exe' pack "T:\agent01\w\e21f69818d8a7e42\src\MyDotNetProject\obj\octopacking\MyDotNetProject.nuspec" -NoPackageAnalysis -BasePath "T:\agent01\w\e21f69818d8a7e42\src\MyDotNetProject" -OutputDirectory "T:\agent01\w\e21f69818d8a7e42\src\MyDotNetProject\obj\octopacked" -Version 1.0.1 -Properties "Configuration=Release"
error OCT-1676060969: System.Exception: There was an error calling NuGet. Please see the output above for more details. Command line: 'T:\agent01\w\e21f69818d8a7e42\packages\OctoPack.3.6.3\build\nuget.exe' pack "T:\agent01\w\e21f69818d8a7e42\src\MyDotNetProject\obj\octopacking\MyDotNetProject.nuspec" -NoPackageAnalysis -BasePath "T:\agent01\w\e21f69818d8a7e42\src\MyDotNetProject" -OutputDirectory "T:\agent01\w\e21f69818d8a7e42\src\MyDotNetProject\obj\octopacked" -Version 1.0.1 -Properties "Configuration=Release"
at OctoPack.Tasks.CreateOctoPackPackage.RunNuGet(String specFilePath, String octopacking, String octopacked, String projectDirectory) in Z:\buildAgent\workDir\20ba9f2e0d5e4022\source\OctoPack.Tasks\CreateOctoPackPackage.cs:line 620
at OctoPack.Tasks.CreateOctoPackPackage.Execute() in Z:\buildAgent\workDir\20ba9f2e0d5e4022\source\OctoPack.Tasks\CreateOctoPackPackage.cs:line 195
```

The repository tag is present in the most recent nuspec.xsd:
https://github.com/NuGet/NuGet.Client/blob/dev/src/NuGet.Core/NuGet.Packaging/compiler/resources/nuspec.xsd#L67

It seems OctoPack / Octo.exe is using an outdated version of the nuspec.xsd (or an old version of nuget.core).

Thanks,

Caio Proiete
https://github.com/caioproiete