CrowdStrike Resource Provider
The CrowdStrike Resource Provider lets you manage crowdstrike resources.
Installing
This package is available for several languages/platforms:
Node.js (JavaScript/TypeScript)
To use from JavaScript or TypeScript in Node.js, install using either npm:
npm install @crowdstrike/pulumi
or yarn:
yarn add @crowdstrike/pulumi
Python
To use from Python, install using pip:
pip install crowdstrike_pulumi
Go
To use from Go, use go get to grab the latest version of the library:
go get github.com/crowdstrike/pulumi-crowdstrike/sdk/go/...
.NET
To use from .NET, install using dotnet add package:
dotnet add package CrowdStrike.Crowdstrike
Reference
For detailed reference documentation, please visit the Pulumi registry.
Metadata
Release files for crowdstrike-pulumi 0.0.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| crowdstrike_pulumi-0.0.14.tar.gz | 119.0 kB | Without provenance | Details |
Release files / crowdstrike_pulumi-0.0.14.tar.gz
| Download URL | crowdstrike_pulumi-0.0.14.tar.gz |
|---|---|
| Size | 119.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32d060c039fa173d62bc1ea3bc6c5349392d93016e7e76634d8a3f5a8d923fd5
|
|
BLAKE2b-256 checksum How to use checksums |
ea3d16d18b36002b6af04161d8dbc62e9d1d759ebe26fbab6bd0ade4d27eac58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for crowdstrike-pulumi 0.0.14
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.