Update Valid Target Platforms#11
Conversation
Update Start-Action1PackageUpload $Platform parameter's ValidateSet to include the new 'Windows_ARM64', 'Mac_IntelCPU', and 'Mac_AppleSilicon' options as specified in the api docs here https://app.action1.com/apidocs/#/Software%20Repository.%20Upload%20Installation%20File/packages_all_packageId_versions_versionId_upload_post.
There was a problem hiding this comment.
At this time the upload function is a part of future function as POC, it bears no functional value at this time. These will be added when that function is fully fleshed out. The PSAction1 module does not currently target the full specification, it is centered on specific customers greatest needs.
There was a problem hiding this comment.
Ah, That makes sense. I'm working on a script that implements the full API doc now for updating our custom packages directly from vendor feeds and figured I'd chip in on this project whenever I ran into issues. Thanks for all your hard work!
|
It’s on the to-do list, but if you share what you come up with I will get it incorporated.
We build that on a per needed function basis so it is not a full implementation, as much of what would be implemented would be needed by so few. Custom app packaging was on the to-do list as you can see the upload was just one phase, templating the software and version was to be next. As it is largely just JSON like everything else.
…--
Gene
From: Esnapp ***@***.***>
Sent: Wednesday, August 20, 2025 4:53 PM
To: Action1Corp/PSAction1 ***@***.***>
Cc: Gene Moody ***@***.***>; Comment ***@***.***>
Subject: Re: [Action1Corp/PSAction1] Update Valid Target Platforms (PR #11)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@Esnapp commented on this pull request.
________________________________
On PSAction1.psm1<#11 (comment)>:
Ah, That makes sense. I'm working on a script that implements the full API doc now for updating our custom packages directly from vendor feeds and figured I'd chip in on this project whenever I ran into issues. Thanks for all your hard work!
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BDMI4L4J5I4ONHAWYBLB6IT3OTU5RAVCNFSM6AAAAACEMM75HOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTCMZYGM3TENZSGE>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Added and updated URI lookups and logic to support Getting (G_) Updating (U_) and New (N_) packages and versions. Improved Start-Action1PackageUpload to update version metadata after upload and handle resume logic more robustly. Extended Get-Action1, New-Action1, and Update-Action1 to support new 'Package' and 'Version' operations, including proper field filtering and path construction.
Added a new URI lookup for single version retrieval and refactored the logic in Start-Action1PackageUpload to simplify updating the uploaded file reference. Improved Get-Action1 to support nested object queries with secondary IDs and streamlined argument handling for URI construction from nest if statements to a switch based arglist splat.
|
I've got this fleshed out and working with my test cases, that said I don't have a great way to test the resume functionality as I've yet to run into a 500 series error while uploading a file. Let me know if you have any thoughts or suggestions and I can take a look at them and see if I can smooth anything out. |
Added explicit error messages when required parameters (Id2 for Package_ID and Id for Object_ID) are not provided in Get-Action1. Also removed an incorrect check for the Query flag not equaling 'Settings' inside an if block that already checks for Query -eq 'Settings' Cleaned up unnecessary blank lines for better readability.
Get-Action1 valid set expected CutomAttribute instead of CustomAttribute
3 participants
Update Start-Action1PackageUpload $Platform parameter's ValidateSet to include the new 'Windows_ARM64', 'Mac_IntelCPU', and 'Mac_AppleSilicon' options as specified in the api docs here https://app.action1.com/apidocs/#/Software%20Repository.%20Upload%20Installation%20File/packages_all_packageId_versions_versionId_upload_post.