Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Add end_of_life parameter support for assets #23

Open
JacobChabot opened this issue Sep 10, 2024 · 0 comments
Open

Feature: Add end_of_life parameter support for assets #23

JacobChabot opened this issue Sep 10, 2024 · 0 comments

Comments

@JacobChabot
Copy link

Expected Behavior

I am trying to set the end-of-life field but the module does not accept the parameter -end_of_life. I want to do: Set-FreshServiceAsset -display_id "15" -end_of_life "2029-01-01"

Current Behavior

In the code on the github page, it is listed as a parameter and the Get/Set-FreshServiceAsset response lists the end-of-life field. If you currently call it with the -end_of_life flag it says it does not accept this parameter.

Possible Solution

Steps to Reproduce (for bugs)

  1. Import the FreshservicePS Module
  2. Connect to the Freshservice API using the module
  3. Obtain a valid display_id for an asset in your Freshservice instance
  4. Use the following code: Set-FreshServiceAsset -display_id "15" -end_of_life "2029-01-01"
  5. Receive the following error: Set-FreshServiceAsset : A parameter cannot be found that matches parameter name 'end_of_life'.

Context

I am creating a script that is automating our hardware provisioning. When we receive a new computer, I want to run this script and set several fields, one of them being the end-of-life based on our refresh policy. I currently have the asset state, name, location, and user assigned to it the last field I need is eol.

Your Environment

  • Module version used: 0.1.6
  • Operating System and PowerShell version: Win 11 23H2 and PSVersion 5.1.22621.39
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

No branches or pull requests

1 participant