Skip to content

Removing deprecated APIs#610

Open
johannesconsulting wants to merge 1 commit into
pspete:devfrom
johannesconsulting:cleanup
Open

Removing deprecated APIs#610
johannesconsulting wants to merge 1 commit into
pspete:devfrom
johannesconsulting:cleanup

Conversation

@johannesconsulting
Copy link
Copy Markdown
Contributor

Description

This PR removed old APIs that are not included in current supported CyberArk version or are removed from documentation.
Its mostly some Gen1 APIs and some APIs that are completely removed.
Doing this cleanup will reduce the codebase and also make it easier for the user to see what parameters can actually be used without being met with errors.
Thinking that most new downloads are using modern supported version of CyberArk and they wont be impacted by these changes.
It makes it a bit easier for us to manage the project too.

I also included a small fix for Set-PASUser. Its currently bugged because the function doesn't send the allowedauthenticationmethods in a array, causing the API to complain if you don't include it.

I tested all the functions manually too, and it worked on 15.0 without issues.

For the sake of transparency, I used assistance from AI for the *.Tests.ps1.
For the actual functions, I did that manually.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that makes existing functionality work differently)
  • Documentation update (psPAS website or command help content)
  • Other (see description)

How Has This Been Tested?

  • Pester test(s) update required
  • Pester test(s) updated
  • Pester test(s) passing

Test Configuration:

  • PowerShell version: 7
  • CyberArk PAS version: 15.0
  • OS Version: Windows Server 2022

Checklist:

  • My code follows the style guidelines of this project
  • I have followed the contributing guidelines.
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new test failures or errors
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have opened & linked a related issue
  • I have linked a related issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant