It does not exist yet, I've filed BM-3326 to add it in v6.1.2

We will make this change for the next minor version (i.e. the next version unless there is pressing need to do a maintenance release before then).

The tracking issue for this is: OT-291

Thank you for the report, I have filed OT-290 to get this fixed.

Apologies for the delay, I had to reach out to gather this information. What I learned was that this was a custom operation. Below is the link to its source:

---

Yes, I made that operation to accommodate DSC Configuration scripts (multiple DSC operations encapsulated in a PowerShell script).

I had built this on a fork of of inedox-windows. I just merged in the latest changes for the main master (it has been 6 months, so there quite a few changes). I have built it, but have not tested it since the merge.

https://github.com/MarkRobertJohnson/inedox-windows/blob/dsc-ensure-config/Windows/InedoExtension/Operations/EnsurePSDscScriptOperation.cs

Thanks, I've filed this as a bug here: BM-3307

Both are supposed to be supported, and quickly inspecting the code itself, I see both as possible arguments:

isMatch("builds") || isMatch("packages")

and

BuildId = AH.ParseInt(request["buildId"] ?? request["packageId"]),
BuildNumber = request["buildNumber"] ?? request["packageNumber"],

Perhaps it's JSON parsing related? Are you POSTing as application/json?

Both of these package types will be supported in 5.2.

PyPI support has now been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

PyPI support has now been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

PyPI support has been added and published as a pre-release version of 5.2.0. Visit the ProGet Versions page to download, or get it from the Inedo Hub download.

There are 2 ways to go about this:

1. Allow $PsCredentials() to support credential names as an argument

This is easiest, but would still require the "allow $CredentialProperty usage" option because you could always just write out the password in PowerShell regardless:

 $credentials = Get-Credential
 [Runtime.InteropServices.Marshal]::PtrToStringAuto([Runtime.InteropServices.Marshal]::SecureStringToBSTR(($credentials.Password))) | Write-Host

2. Create a new PowerShellCredentials type

While the same "exploit" would still be available, at least it would be limited to PowerShell, e.g. you couldn't just Log-Information $CredentialProperty(secret, Password);

This though means we're just duplicating what UserNamePassword credentials already do, and it could cause confusion as to which one to use.

If you have any other feedback on this, we are all ears!

@Adam - I have filed https://github.com/Inedo/inedox-windows/issues/70 to update the existing function to support referencing UsernamePassword credentials so you don't need to use $CredentialProperty

Thank you for the report, this is resolved via: PG-1447

This has also been reported in our Jenkins extensions issues section, can you take a moment to respond to the questions I posed here?

https://github.com/Inedo/inedox-jenkins/issues/26#issuecomment-454188149

Thank you for reporting this - we've determined the root cause and will issue a fix for this ASAP.

Apologies - I broke that endpoint earlier ironically by accidentally disabling logging :(

It should work now; I also note that you can request a key at https://my.inedo.com and manually enter it.

Here is a working PowerShell example (v6.1+):

Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/builds/deploy?applicationName=ApiTest&releaseNumber=1.2.3&buildNumber=1&key=<api-key>"

For pre-v6.1 versions, the equivalent is:

Invoke-RestMethod -Method POST -Uri "http://{bmserver:port}/api/releases/packages/deploy?applicationName=ApiTest&releaseNumber=1.2.3&packageNumber=1&key=<api-key>"

I have also put in a doc change request to clarify the endpoint names.

Additional note: -UseDefaultCredentials would be required if Integrated Authentication were enabled.

Hello Attila,

If you run docker inspect proget -f '{{json .Mounts}}', does it include /var/proget/extensions as both the source and destination of one of the bind mounts?

Python and Debian feeds will be officially rolled out with our v5.2 release in March 2019. See the Products Roadmap for more information.

Good idea, I thought we already had the ability to do that, but I was confusing it with Job History.

Here is the associated issue: OT-278

This will be resolved as part of: OT-274

The workaround is to browse to the URL directly, e.g .

http://{otter-host}/executions/logs?executionId={execId}&level=0&download={true/false}