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

Invoke-VcWorkflow fails with Discovery Workflow (should be pointed to /v1/machines vs. /v1/machineIdentities) #275

Closed
R3LentL355 opened this issue Apr 29, 2024 · 1 comment

Comments

@R3LentL355
Copy link
Contributor

Environment

Full Operating System: Tested on Windows 10
VenafiPS version: 6.3.1
PowerShell version: 7.4.2
TLSPDC version (if applicable): N/A

Steps to reproduce

Execute: Invoke-VcWorkflow -Workflow Discover

Actual behavior

Error Message: "Unable to find machineIdentity XXXXX"

The API call being made is pointed at the "machineIdentities" endpoint. For Discover, it should be "machines". I have validated that I get the same results outside of PowerShell:

Screenshot 2024-04-29 at 3 13 12 PM

There appears to be a documentation/OpenAPI bug on https://developer.venafi.com for this specific workflow as well. I have submitted documentation feedback to have this addressed.

Screenshots

Screenshot 2024-04-29 at 3 10 49 PM

@gdbarron
Copy link
Collaborator

Closed by #276

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

2 participants