automatic import of python-django-kms-field

1 files changed, 180 insertions, 0 deletions

diff --git a/python-django-kms-field.spec b/python-django-kms-field.spec
new file mode 100644
index 0000000..086bc88
--- /dev/null
+++ b/python-django-kms-field.spec
@@ -0,0 +1,180 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-django-kms-field
+Version:	0.6
+Release:	1
+Summary:	Add Amazon KMS encrypted database fields
+License:	The MIT License: http://www.opensource.org/licenses/mit-license.php
+URL:		https://github.com/skruger/django-kms-field
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/9f/7a/502e3360421bbbafd82a7dc8dd7a366d3fd6ec7b2302879697342dc9e26c/django-kms-field-0.6.tar.gz
+BuildArch:	noarch
+
+
+%description
+# django-kms-field
+[![Build Status](https://travis-ci.org/skruger/django-kms-field.svg?branch=master)](https://travis-ci.org/skruger/django-kms-field)
+
+KMS encrypted database field for Django.
+
+The KMSEncryptedCharField uses your KMS key to encrypt your
+data before it is stored in the database and it decrypts it again
+when you read from the database.
+
+It was designed with stored credentials and other critical
+private data in mind. I would strongly recommend thinking
+about which models use this field with as it has not been
+optomized for high volume access and boto api calls
+during query time may impact performance. Splitting secure
+fields into separate models can improve performance
+significantly as opposed to putting encrypted fields in
+frequently read and saved models.
+
+### Example
+```python
+from django.db import models
+from django_kms.fields import KMSEncryptedCharField
+
+
+class StoredCredential(models.Model):
+    description = models.CharField(max_length=50)
+    username = models.CharField(max_length=50)
+    password = KMSEncryptedCharField(key_id="alias/my_key")
+
+```
+
+### Django settings
+```python
+KMS_FIELD_KEY = 'alias/<my-key>'
+KMS_FIELD_REGION = 'us-west-2'
+KMS_FIELD_CACHE_SIZE = 500  # Number of decrypted plaintext values to hold in memory
+```
+
+%package -n python3-django-kms-field
+Summary:	Add Amazon KMS encrypted database fields
+Provides:	python-django-kms-field
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-django-kms-field
+# django-kms-field
+[![Build Status](https://travis-ci.org/skruger/django-kms-field.svg?branch=master)](https://travis-ci.org/skruger/django-kms-field)
+
+KMS encrypted database field for Django.
+
+The KMSEncryptedCharField uses your KMS key to encrypt your
+data before it is stored in the database and it decrypts it again
+when you read from the database.
+
+It was designed with stored credentials and other critical
+private data in mind. I would strongly recommend thinking
+about which models use this field with as it has not been
+optomized for high volume access and boto api calls
+during query time may impact performance. Splitting secure
+fields into separate models can improve performance
+significantly as opposed to putting encrypted fields in
+frequently read and saved models.
+
+### Example
+```python
+from django.db import models
+from django_kms.fields import KMSEncryptedCharField
+
+
+class StoredCredential(models.Model):
+    description = models.CharField(max_length=50)
+    username = models.CharField(max_length=50)
+    password = KMSEncryptedCharField(key_id="alias/my_key")
+
+```
+
+### Django settings
+```python
+KMS_FIELD_KEY = 'alias/<my-key>'
+KMS_FIELD_REGION = 'us-west-2'
+KMS_FIELD_CACHE_SIZE = 500  # Number of decrypted plaintext values to hold in memory
+```
+
+%package help
+Summary:	Development documents and examples for django-kms-field
+Provides:	python3-django-kms-field-doc
+%description help
+# django-kms-field
+[![Build Status](https://travis-ci.org/skruger/django-kms-field.svg?branch=master)](https://travis-ci.org/skruger/django-kms-field)
+
+KMS encrypted database field for Django.
+
+The KMSEncryptedCharField uses your KMS key to encrypt your
+data before it is stored in the database and it decrypts it again
+when you read from the database.
+
+It was designed with stored credentials and other critical
+private data in mind. I would strongly recommend thinking
+about which models use this field with as it has not been
+optomized for high volume access and boto api calls
+during query time may impact performance. Splitting secure
+fields into separate models can improve performance
+significantly as opposed to putting encrypted fields in
+frequently read and saved models.
+
+### Example
+```python
+from django.db import models
+from django_kms.fields import KMSEncryptedCharField
+
+
+class StoredCredential(models.Model):
+    description = models.CharField(max_length=50)
+    username = models.CharField(max_length=50)
+    password = KMSEncryptedCharField(key_id="alias/my_key")
+
+```
+
+### Django settings
+```python
+KMS_FIELD_KEY = 'alias/<my-key>'
+KMS_FIELD_REGION = 'us-west-2'
+KMS_FIELD_CACHE_SIZE = 500  # Number of decrypted plaintext values to hold in memory
+```
+
+%prep
+%autosetup -n django-kms-field-0.6
+
+%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-django-kms-field -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Wed May 10 2023 Python_Bot <Python_Bot@openeuler.org> - 0.6-1
+- Package Spec generated