automatic import of python-pulumi-vaultopeneuler20.03

3 files changed, 311 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..d672962 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/pulumi_vault-5.11.0.tar.gz
diff --git a/python-pulumi-vault.spec b/python-pulumi-vault.spec
new file mode 100644
index 0000000..c36c1b1
--- /dev/null
+++ b/python-pulumi-vault.spec
@@ -0,0 +1,309 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-pulumi-vault
+Version:	5.11.0
+Release:	1
+Summary:	A Pulumi package for creating and managing HashiCorp Vault cloud resources.
+License:	Apache-2.0
+URL:		https://pulumi.io
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/6a/22/cb0e7aa26c7ae43242224d965238e9c8d5c559ba04c1304630c5c3f7b0d3/pulumi_vault-5.11.0.tar.gz
+BuildArch:	noarch
+
+
+%description
+[![Build Status](https://travis-ci.com/pulumi/pulumi-vault.svg?token=eHg7Zp5zdDDJfTjY8ejq&branch=master)](https://travis-ci.com/pulumi/pulumi-vault)
+
+# Hashicorp Vault Resource Provider
+
+The Vault resource provider for Pulumi lets you manage Vault resources in your cloud programs. To use
+this package, please [install the Pulumi CLI first](https://pulumi.io/).
+
+## 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/vault
+
+or `yarn`:
+
+    $ yarn add @pulumi/vault
+
+### Python
+
+To use from Python, install using `pip`:
+
+    $ pip install pulumi_vault
+
+### Go
+
+To use from Go, use `go get` to grab the latest version of the library
+
+    $ go get github.com/pulumi/pulumi-vault/sdk/v4
+
+### .NET
+
+To use from .NET, install using `dotnet add package`:
+
+    $ dotnet add package Pulumi.Vault
+
+## Configuration
+
+The following configuration points are available:
+
+- `vault:address` - (Required) Origin URL of the Vault server. This is a URL with a scheme, a hostname and a port but with no path.
+  May be set via the `VAULT_ADDR` environment variable.
+- `vault:token` - (Required) Vault token that will be used by the provider to authenticate. May be set via the `VAULT_TOKEN`
+  environment variable. If none is otherwise supplied, the provider will attempt to read it from ~/.vault-token (where the vault
+  command stores its current token). The provider will issue itself a new token that is a child of the one given, with a short TTL
+  to limit the exposure of any requested secrets. Note that the given token must have the update capability on the `auth/token/create`
+  path in Vault in order to create child tokens.
+- `vault:tokenName` - (Optional) Token name to use for creating the Vault child token. May be set via the `VAULT_TOKEN_NAME`
+  environment variable. 
+- `vault:ca_cert_file` - (Optional) Path to a file on local disk that will be used to validate the certificate presented by
+  the Vault server. May be set via the `VAULT_CACERT` environment variable.
+- `vault:ca_cert_dir` - (Optional) Path to a directory on local disk that contains one or more certificate files that will
+  be used to validate the certificate presented by the Vault server. May be set via the `VAULT_CAPATH` environment variable.
+- `vault:client_auth` - (Optional) A configuration block, described below, that provides credentials used by the provider
+  to authenticate with the Vault server. At present there is little reason to set this, because the provider does not 
+  support the TLS certificate authentication mechanism.
+    - `vault:cert_file` - (Required) Path to a file on local disk that contains the PEM-encoded certificate to present to the server.
+    - `vault:key_file` - (Required) Path to a file on local disk that contains the PEM-encoded private key for which the 
+    authentication certificate was issued.
+- `vault:skip_tls_verify` - (Optional) Set this to true to disable verification of the Vault server's TLS certificate. This
+  is strongly discouraged except in prototype or development environments, since it exposes the possibility that the provider
+  can be tricked into writing secrets to a server controlled by an intruder. May be set via the `VAULT_SKIP_VERIFY` environment variable.
+- `vault:max_lease_ttl_seconds` - (Optional) Used as the duration for the intermediate Vault token the provider issues itself,
+  which in turn limits the duration of secret leases issued by Vault. Defaults to `20` minutes and may be set via the 
+  `TERRAFORM_VAULT_MAX_TTL` environment variable. See the section above on Using Vault credentials in the provider configuration
+  for the implications of this setting.
+- `vault:max_retries` - (Optional) Used as the maximum number of retries when a 5xx error code is encountered. Defaults to `2`
+  retries and may be set via the VAULT_MAX_RETRIES environment variable.
+- `vault:namespace` - (Optional) Set the namespace to use. May be set via the `VAULT_NAMESPACE` environment variable. Available
+  only for Vault Enterprise.
+
+## Reference
+
+For further information, please visit [the Vault provider docs](https://www.pulumi.com/docs/intro/cloud-providers/vault) or for detailed reference documentation, please visit [the API docs](https://www.pulumi.com/docs/reference/pkg/vault).
+
+
+
+
+%package -n python3-pulumi-vault
+Summary:	A Pulumi package for creating and managing HashiCorp Vault cloud resources.
+Provides:	python-pulumi-vault
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-pulumi-vault
+[![Build Status](https://travis-ci.com/pulumi/pulumi-vault.svg?token=eHg7Zp5zdDDJfTjY8ejq&branch=master)](https://travis-ci.com/pulumi/pulumi-vault)
+
+# Hashicorp Vault Resource Provider
+
+The Vault resource provider for Pulumi lets you manage Vault resources in your cloud programs. To use
+this package, please [install the Pulumi CLI first](https://pulumi.io/).
+
+## 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/vault
+
+or `yarn`:
+
+    $ yarn add @pulumi/vault
+
+### Python
+
+To use from Python, install using `pip`:
+
+    $ pip install pulumi_vault
+
+### Go
+
+To use from Go, use `go get` to grab the latest version of the library
+
+    $ go get github.com/pulumi/pulumi-vault/sdk/v4
+
+### .NET
+
+To use from .NET, install using `dotnet add package`:
+
+    $ dotnet add package Pulumi.Vault
+
+## Configuration
+
+The following configuration points are available:
+
+- `vault:address` - (Required) Origin URL of the Vault server. This is a URL with a scheme, a hostname and a port but with no path.
+  May be set via the `VAULT_ADDR` environment variable.
+- `vault:token` - (Required) Vault token that will be used by the provider to authenticate. May be set via the `VAULT_TOKEN`
+  environment variable. If none is otherwise supplied, the provider will attempt to read it from ~/.vault-token (where the vault
+  command stores its current token). The provider will issue itself a new token that is a child of the one given, with a short TTL
+  to limit the exposure of any requested secrets. Note that the given token must have the update capability on the `auth/token/create`
+  path in Vault in order to create child tokens.
+- `vault:tokenName` - (Optional) Token name to use for creating the Vault child token. May be set via the `VAULT_TOKEN_NAME`
+  environment variable. 
+- `vault:ca_cert_file` - (Optional) Path to a file on local disk that will be used to validate the certificate presented by
+  the Vault server. May be set via the `VAULT_CACERT` environment variable.
+- `vault:ca_cert_dir` - (Optional) Path to a directory on local disk that contains one or more certificate files that will
+  be used to validate the certificate presented by the Vault server. May be set via the `VAULT_CAPATH` environment variable.
+- `vault:client_auth` - (Optional) A configuration block, described below, that provides credentials used by the provider
+  to authenticate with the Vault server. At present there is little reason to set this, because the provider does not 
+  support the TLS certificate authentication mechanism.
+    - `vault:cert_file` - (Required) Path to a file on local disk that contains the PEM-encoded certificate to present to the server.
+    - `vault:key_file` - (Required) Path to a file on local disk that contains the PEM-encoded private key for which the 
+    authentication certificate was issued.
+- `vault:skip_tls_verify` - (Optional) Set this to true to disable verification of the Vault server's TLS certificate. This
+  is strongly discouraged except in prototype or development environments, since it exposes the possibility that the provider
+  can be tricked into writing secrets to a server controlled by an intruder. May be set via the `VAULT_SKIP_VERIFY` environment variable.
+- `vault:max_lease_ttl_seconds` - (Optional) Used as the duration for the intermediate Vault token the provider issues itself,
+  which in turn limits the duration of secret leases issued by Vault. Defaults to `20` minutes and may be set via the 
+  `TERRAFORM_VAULT_MAX_TTL` environment variable. See the section above on Using Vault credentials in the provider configuration
+  for the implications of this setting.
+- `vault:max_retries` - (Optional) Used as the maximum number of retries when a 5xx error code is encountered. Defaults to `2`
+  retries and may be set via the VAULT_MAX_RETRIES environment variable.
+- `vault:namespace` - (Optional) Set the namespace to use. May be set via the `VAULT_NAMESPACE` environment variable. Available
+  only for Vault Enterprise.
+
+## Reference
+
+For further information, please visit [the Vault provider docs](https://www.pulumi.com/docs/intro/cloud-providers/vault) or for detailed reference documentation, please visit [the API docs](https://www.pulumi.com/docs/reference/pkg/vault).
+
+
+
+
+%package help
+Summary:	Development documents and examples for pulumi-vault
+Provides:	python3-pulumi-vault-doc
+%description help
+[![Build Status](https://travis-ci.com/pulumi/pulumi-vault.svg?token=eHg7Zp5zdDDJfTjY8ejq&branch=master)](https://travis-ci.com/pulumi/pulumi-vault)
+
+# Hashicorp Vault Resource Provider
+
+The Vault resource provider for Pulumi lets you manage Vault resources in your cloud programs. To use
+this package, please [install the Pulumi CLI first](https://pulumi.io/).
+
+## 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/vault
+
+or `yarn`:
+
+    $ yarn add @pulumi/vault
+
+### Python
+
+To use from Python, install using `pip`:
+
+    $ pip install pulumi_vault
+
+### Go
+
+To use from Go, use `go get` to grab the latest version of the library
+
+    $ go get github.com/pulumi/pulumi-vault/sdk/v4
+
+### .NET
+
+To use from .NET, install using `dotnet add package`:
+
+    $ dotnet add package Pulumi.Vault
+
+## Configuration
+
+The following configuration points are available:
+
+- `vault:address` - (Required) Origin URL of the Vault server. This is a URL with a scheme, a hostname and a port but with no path.
+  May be set via the `VAULT_ADDR` environment variable.
+- `vault:token` - (Required) Vault token that will be used by the provider to authenticate. May be set via the `VAULT_TOKEN`
+  environment variable. If none is otherwise supplied, the provider will attempt to read it from ~/.vault-token (where the vault
+  command stores its current token). The provider will issue itself a new token that is a child of the one given, with a short TTL
+  to limit the exposure of any requested secrets. Note that the given token must have the update capability on the `auth/token/create`
+  path in Vault in order to create child tokens.
+- `vault:tokenName` - (Optional) Token name to use for creating the Vault child token. May be set via the `VAULT_TOKEN_NAME`
+  environment variable. 
+- `vault:ca_cert_file` - (Optional) Path to a file on local disk that will be used to validate the certificate presented by
+  the Vault server. May be set via the `VAULT_CACERT` environment variable.
+- `vault:ca_cert_dir` - (Optional) Path to a directory on local disk that contains one or more certificate files that will
+  be used to validate the certificate presented by the Vault server. May be set via the `VAULT_CAPATH` environment variable.
+- `vault:client_auth` - (Optional) A configuration block, described below, that provides credentials used by the provider
+  to authenticate with the Vault server. At present there is little reason to set this, because the provider does not 
+  support the TLS certificate authentication mechanism.
+    - `vault:cert_file` - (Required) Path to a file on local disk that contains the PEM-encoded certificate to present to the server.
+    - `vault:key_file` - (Required) Path to a file on local disk that contains the PEM-encoded private key for which the 
+    authentication certificate was issued.
+- `vault:skip_tls_verify` - (Optional) Set this to true to disable verification of the Vault server's TLS certificate. This
+  is strongly discouraged except in prototype or development environments, since it exposes the possibility that the provider
+  can be tricked into writing secrets to a server controlled by an intruder. May be set via the `VAULT_SKIP_VERIFY` environment variable.
+- `vault:max_lease_ttl_seconds` - (Optional) Used as the duration for the intermediate Vault token the provider issues itself,
+  which in turn limits the duration of secret leases issued by Vault. Defaults to `20` minutes and may be set via the 
+  `TERRAFORM_VAULT_MAX_TTL` environment variable. See the section above on Using Vault credentials in the provider configuration
+  for the implications of this setting.
+- `vault:max_retries` - (Optional) Used as the maximum number of retries when a 5xx error code is encountered. Defaults to `2`
+  retries and may be set via the VAULT_MAX_RETRIES environment variable.
+- `vault:namespace` - (Optional) Set the namespace to use. May be set via the `VAULT_NAMESPACE` environment variable. Available
+  only for Vault Enterprise.
+
+## Reference
+
+For further information, please visit [the Vault provider docs](https://www.pulumi.com/docs/intro/cloud-providers/vault) or for detailed reference documentation, please visit [the API docs](https://www.pulumi.com/docs/reference/pkg/vault).
+
+
+
+
+%prep
+%autosetup -n pulumi-vault-5.11.0
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-pulumi-vault -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 5.11.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..f7e768b
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+423ef47b9ec661b3275e858de0bee598  pulumi_vault-5.11.0.tar.gz