This release is a pre-release and may not be stable for production use.
Artifactory Resource Provider
The Artifactory Resource Provider lets you manage Artifactory resources.
Installing
This package is available in many languages in the standard packaging formats.
Node.js (Java/TypeScript)
To use from JavaScript or TypeScript in Node.js, install using either npm:
$ npm install @pulumi/artifactory
or yarn:
$ yarn add @pulumi/artifactory
Python
To use from Python, install using pip:
$ pip install pulumi_artifactory
Go
To use from Go, use go get to grab the latest version of the library
$ go get github.com/pulumi/pulumi-artifactory/sdk/v8
.NET
To use from .NET, install using dotnet add package:
$ dotnet add package Pulumi.Artifactory
Configuration
The following configuration points are available:
artifactory:url- (Required) URL of Artifactory. This can also be sourced from theARTIFACTORY_URLenvironment variable.artifactory:username- (Optional) Username for basic auth. Requires password to be set. Conflicts withapiKey, andaccessToken. This can also be sourced from theARTIFACTORY_USERNAMEenvironment variable.artifactory:password- (Optional) Password for basic auth. Requires username to be set. Conflicts withapiKey, andaccessToken. This can also be sourced from theARTIFACTORY_PASSWORDenvironment variable.artifactory:apiKey- (Optional) API key for api auth. UsesX-JFrog-Art-Apiheader. Conflicts withusername,password, andaccessToken. This can also be sourced from theARTIFACTORY_API_KEYenvironment variable.artifactory:accessToken- (Optional) API key for token auth. UsesAuthorization: Bearerheader. For xray functionality, this is the only auth method accepted. Conflicts withusernameandpassword, andapiKey. This can also be sourced from theARTIFACTORY_ACCESS_TOKENenvironment variable.
Reference
For further information, please visit the Artifactory provider docs or for detailed reference documentation, please visit the API docs.
1 maintainer
Metadata
1 maintainer
Release files for pulumi-artifactory 8.11.0a1776923600
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 | |
|---|---|---|---|---|
| pulumi_artifactory-8.11.0a1776923600.tar.gz | 1.2 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pulumi_artifactory-8.11.0a1776923600-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.1 MB
Release files / pulumi_artifactory-8.11.0a1776923600.tar.gz
| Download URL | pulumi_artifactory-8.11.0a1776923600.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
19404f324f48315ab966ff0cb3ee95ef4e925094656b64b4d6e1b9a6f1715a25
|
|
BLAKE2b-256 checksum How to use checksums |
b097c348910425e2f4a28000a2cfed10c6ba51674cb51860716e010a1f2343c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.8
|
Release files / pulumi_artifactory-8.11.0a1776923600-py3-none-any.whl
| Download URL | pulumi_artifactory-8.11.0a1776923600-py3-none-any.whl |
|---|---|
| Size | 1.9 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0680032a25cc27d0cf5dc233b27d4e0225bde1b5e5c63f02a9f15fc6d5c76405
|
|
BLAKE2b-256 checksum How to use checksums |
654996c2ee496ae0a56a9b44b1bf339b0d93721a74bee233639bd862d33a941e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.8
|
Security for pulumi-artifactory 8.11.0a1776923600
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
