Skip to content
This repository has been archived by the owner on Aug 25, 2024. It is now read-only.

Get-SmaArchiveAsset does not properly return archived assets #9

Open
ArtisanByteCrafter opened this issue Apr 18, 2019 · 1 comment
Assignees
Labels
bug Something isn't working upstream caused by an upstream dependency

Comments

@ArtisanByteCrafter
Copy link
Owner

ArtisanByteCrafter commented Apr 18, 2019

I can successfully retrieve the archival status of an asset with Get-SmaAsset, using -QueryParameters "?filtering=asset.archive eq completed,asset.id eq 1234", however, running Get-SmaArchiveAsset against the same AssetID returns a 500 error.

Working Endpoint:

"/api/asset/assets?filtering=asset.archive eq completed,asset.id eq 1234"

Not Working Endpoint:

"/api/asset/archived_devices/<AssetID>"

Steps to reproduce:

Error:

Get-SmaArchiveAsset -Server 'https://kace.example.com' -Credential (Get-Credential) -AssetID 1234

- Invoke-RestMethod : The remote server returned an error: (500) Internal Server Error.

Workaround using Get-SmaAsset with filter:

Get-SmaAsset -Server 'https://kace.example.com' -Credential (Get-Credential) -QueryParameters "?filtering=asset.archive eq completed,asset.id eq 1234"

+ Returns successfully
 
@ArtisanByteCrafter ArtisanByteCrafter added the bug Something isn't working label Apr 18, 2019
@ArtisanByteCrafter ArtisanByteCrafter self-assigned this Apr 18, 2019
@ArtisanByteCrafter ArtisanByteCrafter added the upstream caused by an upstream dependency label Oct 31, 2019
@ArtisanByteCrafter
Copy link
Owner Author

I am removing this from the declared available cmdlets until it can be resolved upstream

ArtisanByteCrafter added a commit that referenced this issue Nov 13, 2019
* added new connect-smaserver cmdlet

* new auth method for New-APIGetRequest

* [WIP-v2.0] Get-SmaMachineInventory

* [WIPv2.0] GET /machines updated

* [WIP-v2.0] version bump in manifest

* [WIP-v2.0]better err handling during auth #23

* remove declaration for get-smaarchiveasset  #9

* [WIPv2.0] GET /assets updated

* updated readme

* [WIP-v2.0] /ManagedInstall and /Reporting updated

* [WIP-v2.0] /PUT cmdlets updated

* removed non-working /api/script endpoint #11

* [WIP-v2.0] /POST requests

* [WIP-v2.0] last group of /GET requests

* [WIP-v2.0] added /DELETE cmdlets

* formatting

* formatting

* convert to external markdown help

* external help xml created

* docs update

* fix external help file?

* get-help -full should resolve now

* get-help -online should open to docs, once merged

* added positional parameters where appropriate #25

* pester tests refactor for new authentication

* azuredevops pipeline stuffs

* Update azure-pipelines.yml for Azure Pipelines

* build fixes

* build fixes

* Update azure-pipelines.yml for Azure Pipelines

* test

* nore fixes

* more build fixes

* Update azure-pipelines.yml for Azure Pipelines

* Update azure-pipelines.yml for Azure Pipelines

* Update azure-pipelines.yml for Azure Pipelines

* Update azure-pipelines.yml for Azure Pipelines

* Update azure-pipelines.yml for Azure Pipelines

* build fixes

* anyone reading these, i'm sorry

* fix psake

* more fix

* psake

* try to get newest v of pester

* fix build output file

* moar fix much hope

* .

* try fix

* Add pwsh (Core) test env

* Update azure-pipelines.yml for Azure Pipelines

* remove unnecessary property from connect-server

* readme updated

* WIP-pipeline-part-1

* clean up readme

* final pipeline refactor

* docs update for new parameters

* Final commit to WIP for v2.0
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working upstream caused by an upstream dependency
Projects
None yet
Development

No branches or pull requests

1 participant