paloaltonetworks / prisma-cloud-go

Prisma Cloud SDK in Go

prisma-cloud-go

Prisma Cloud SDK in Go

prisma-cloud-go's Issues

Add ```fields``` field to alert Request

( not sure where to put this, the documentation seems correct so I guess it only affects this implementation)

Describe the bug

The documentation for the Alerts API specifies a fields field, that's not present in the Request structure in v0.4.2 here.

Expected behavior

That structures in the SDK reflect the API documentation.

Current behavior

The SDK in its current state doesn't reflect the documented API.

Possible solution

Add missing fields.

Steps to reproduce

n/a

Screenshots

Current structure:
type Request struct { TimeRange timerange.TimeRange json:"timeRange"Limit int json:"limit,omitempty"Offset int json:"offset,omitempty"Detailed bool json:"detailed"PageToken string json:"pageToken,omitempty"SortBy []string json:"sortBy,omitempty"Filters []Filter json:"filters,omitempty" }

Context

When calling the API, responses can grow very large, and I'm trying to reduce the memory impact on the client (which crashes sometimes). In order to do this, I'd like to scope down the response to what I need.

Your Environment

• Version used: v0.4.2

Thanks you :)

CloudQuery Source Plugin?

Hi Team, hopefully this is right place to ask, if not, I'd appreciate if you can direct me.

I'm the founder of cloudquery.io, a high performance open source ELT framework.

Our users are interested in a Prisma CloudQuery Source plugin, but as we cannot maintain all the plugins ourselves, I was curious if this would be an interesting collaboration, where we would help implement an initial source plugin, and you will help maintain it.

This will give your users the ability to sync Prisma alerts/apis to any of their datalakes/data-warehouses/databases easily using any of the growing list of CQ destination plugins.

Best,
Yevgeny

Client returns error from `switch resp.StatusCode` for 503 response without retry and fails to unmarshal

Describe the bug

2023-12-12T20:31:26.489Z [ERROR] vertex "prismacloud_policy.example" error: 503 error, and could not unmarshal header "{\"severity\":\"ERROR\",\"i18nKey\":\"service_unavailable\"}": json: cannot unmarshal object into Go value of type []prismacloud.PrismaCloudError

Expected behavior

The provider should retry on 503 status code and correctly unmarshal the header. It seems like the code change may belong within the client status code switch.

Current behavior

On 503 response code, functions such as policy.Get return an error without any retry.

Possible solution

Retry with expontential backoff and if it fails after say, five, attempts return the error.

Steps to reproduce

Use prismacloud in China....

Context

Using the policy resource on the prismacloud terraform provider

Your Environment

PrismaCloud China tends to get a lot of 503 errors.

• Version used: PrismaCloud Terraform provider version 1.5.1
• Environment name and version (e.g. Chrome 59, node.js 5.4, python 3.7.3): Terraform 1.4.4
• Operating System and version (desktop or mobile): Linux container
• Link to your project: https://github.com/PaloAltoNetworks/terraform-provider-prismacloud

[Community Health Assessment] Changes needed

Health Check	Pass	Score	More Info
Contains a meaningful README.md file	✅	20 / 20	More info
SUPPORT.md file exists	✅	20 / 20	More info
Repo has a description	✅	15 / 15	More info
Has a recognized open source license	✅	15 / 15	More info
Has a descriptive repo name	✅	15 / 15	More info
Required topics attached to repo	✅	15 / 15	More info
CONTRIBUTING.md file with contribution guidelines	❌	0 / 5	More info
Has custom issue and pull request templates	❌	0 / 5	More info

Current score: 100
Target threshold: 100
Total possible: 110