automatic import of python-slsmanager

3 files changed, 183 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..13d1946 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/slsmanager-0.2.2.tar.gz
diff --git a/python-slsmanager.spec b/python-slsmanager.spec
new file mode 100644
index 0000000..94ed314
--- /dev/null
+++ b/python-slsmanager.spec
@@ -0,0 +1,181 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-slsmanager
+Version:	0.2.2
+Release:	1
+Summary:	A basic tool that simplifies the deployment of AWS lambda functions
+License:	MIT License
+URL:		https://github.com/AineshSootha/serverlessManager
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/f9/0a/b09b9a098871044b2cea5efb4e0eb6b2bc5b6c9025776e5f04b629ca7f76/slsmanager-0.2.2.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-click
+Requires:	python3-pathlib
+Requires:	python3-colorama
+Requires:	python3-boto3
+Requires:	python3-progress
+Requires:	python3-glob2
+Requires:	python3-pyyaml
+
+%description
+## On your Local Computer (Incomplete):
+- If you wish to use slsmanager from your local computer to create projects/repositories:
+ - Open a terminal window and navigate to the directory with the handler file. 
+- Install serverless-manager on your local machine:
+	- `pip install slsmanager`
+ - Run serverless manager on your terminal:
+	  `slsmanager`
+#### 1. Creating a CodeCommit Repository
+- Follow the instructions to create a CodeCommit Repository and clone it to your directory using the Git Credentials.
+- You can also do this from the AWS console.
+#### 2. Creating a CodeBuild Project
+ - **(OPTION 1: using slsmanager)**
+ ![Steps to create a project](/assets/cbproj.png)
+	- You can use slsmanager to create a CodeBuild Project.
+	- You will need your AWS Access Key ID, your Secret Access Key, the default region and the URL to your CodeCommit Repository
+- **(OPTION 2: using AWS console)**
+	- Follow the steps provided in the first section of this README
+#### 3. Creating the CodePipeline
+- Serverless manager doesn't support the creation of a CodePipeline yet. 
+- Follow the steps provided in the first section of this README
+#### 4. Creating ***serverless.yml*** and ***buildspec.yml*** (INCOMPLETE)
+**Please use the provided buildspec.yml template and do not create a serverless.yml file using slsmanager as it is currently incomplete**
+ If you have a file called ***handlerFun1.js***, and it contains the function firstFun() which you would like to deploy.
+ - Follow the on-screen instructions:
+  ![First Steps](/assets/firstSteps.png)
+	 - Here, I created a service called "CodeCommitTest" 
+	 - I set the AWS-region to us-east-2 (which is what my AWS console is set to). 
+	 - The stage sets the serverless *stage* property.
+	 - The ENV_NAME is the last part of the ENV_NAME_ environment variables (which we set earlier). This will be reflected in the final name of your function on your console. This property allows us to create multiple  deployed versions of the same lambda function source.
+	 - Module name follows the convention ***directory/filename.function***
+	 - The **function name** is the name of the final lambda function (and is set in ***serverless.yml***).
+	 - By default, the only file added to the current lambda function (That will show up on the console) is the handler file provided in the module name. If you would like to include other files in the final lambda function that is deployed, you may edit the newly generated ***serverless.yml*** and add the required files to the **functions/*your_function*/package/patterns**
+	 - You may also edit/add any other properties in ***serverless.yml***
+	 - Finally, the tool generates a buildspec.yml file for your function.
+		 - If you want to deploy all lambda functions present in ***serverless.yml*** you can press **'a'** in the final step. Otherwise, press **'n'**.
+
+%package -n python3-slsmanager
+Summary:	A basic tool that simplifies the deployment of AWS lambda functions
+Provides:	python-slsmanager
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-slsmanager
+## On your Local Computer (Incomplete):
+- If you wish to use slsmanager from your local computer to create projects/repositories:
+ - Open a terminal window and navigate to the directory with the handler file. 
+- Install serverless-manager on your local machine:
+	- `pip install slsmanager`
+ - Run serverless manager on your terminal:
+	  `slsmanager`
+#### 1. Creating a CodeCommit Repository
+- Follow the instructions to create a CodeCommit Repository and clone it to your directory using the Git Credentials.
+- You can also do this from the AWS console.
+#### 2. Creating a CodeBuild Project
+ - **(OPTION 1: using slsmanager)**
+ ![Steps to create a project](/assets/cbproj.png)
+	- You can use slsmanager to create a CodeBuild Project.
+	- You will need your AWS Access Key ID, your Secret Access Key, the default region and the URL to your CodeCommit Repository
+- **(OPTION 2: using AWS console)**
+	- Follow the steps provided in the first section of this README
+#### 3. Creating the CodePipeline
+- Serverless manager doesn't support the creation of a CodePipeline yet. 
+- Follow the steps provided in the first section of this README
+#### 4. Creating ***serverless.yml*** and ***buildspec.yml*** (INCOMPLETE)
+**Please use the provided buildspec.yml template and do not create a serverless.yml file using slsmanager as it is currently incomplete**
+ If you have a file called ***handlerFun1.js***, and it contains the function firstFun() which you would like to deploy.
+ - Follow the on-screen instructions:
+  ![First Steps](/assets/firstSteps.png)
+	 - Here, I created a service called "CodeCommitTest" 
+	 - I set the AWS-region to us-east-2 (which is what my AWS console is set to). 
+	 - The stage sets the serverless *stage* property.
+	 - The ENV_NAME is the last part of the ENV_NAME_ environment variables (which we set earlier). This will be reflected in the final name of your function on your console. This property allows us to create multiple  deployed versions of the same lambda function source.
+	 - Module name follows the convention ***directory/filename.function***
+	 - The **function name** is the name of the final lambda function (and is set in ***serverless.yml***).
+	 - By default, the only file added to the current lambda function (That will show up on the console) is the handler file provided in the module name. If you would like to include other files in the final lambda function that is deployed, you may edit the newly generated ***serverless.yml*** and add the required files to the **functions/*your_function*/package/patterns**
+	 - You may also edit/add any other properties in ***serverless.yml***
+	 - Finally, the tool generates a buildspec.yml file for your function.
+		 - If you want to deploy all lambda functions present in ***serverless.yml*** you can press **'a'** in the final step. Otherwise, press **'n'**.
+
+%package help
+Summary:	Development documents and examples for slsmanager
+Provides:	python3-slsmanager-doc
+%description help
+## On your Local Computer (Incomplete):
+- If you wish to use slsmanager from your local computer to create projects/repositories:
+ - Open a terminal window and navigate to the directory with the handler file. 
+- Install serverless-manager on your local machine:
+	- `pip install slsmanager`
+ - Run serverless manager on your terminal:
+	  `slsmanager`
+#### 1. Creating a CodeCommit Repository
+- Follow the instructions to create a CodeCommit Repository and clone it to your directory using the Git Credentials.
+- You can also do this from the AWS console.
+#### 2. Creating a CodeBuild Project
+ - **(OPTION 1: using slsmanager)**
+ ![Steps to create a project](/assets/cbproj.png)
+	- You can use slsmanager to create a CodeBuild Project.
+	- You will need your AWS Access Key ID, your Secret Access Key, the default region and the URL to your CodeCommit Repository
+- **(OPTION 2: using AWS console)**
+	- Follow the steps provided in the first section of this README
+#### 3. Creating the CodePipeline
+- Serverless manager doesn't support the creation of a CodePipeline yet. 
+- Follow the steps provided in the first section of this README
+#### 4. Creating ***serverless.yml*** and ***buildspec.yml*** (INCOMPLETE)
+**Please use the provided buildspec.yml template and do not create a serverless.yml file using slsmanager as it is currently incomplete**
+ If you have a file called ***handlerFun1.js***, and it contains the function firstFun() which you would like to deploy.
+ - Follow the on-screen instructions:
+  ![First Steps](/assets/firstSteps.png)
+	 - Here, I created a service called "CodeCommitTest" 
+	 - I set the AWS-region to us-east-2 (which is what my AWS console is set to). 
+	 - The stage sets the serverless *stage* property.
+	 - The ENV_NAME is the last part of the ENV_NAME_ environment variables (which we set earlier). This will be reflected in the final name of your function on your console. This property allows us to create multiple  deployed versions of the same lambda function source.
+	 - Module name follows the convention ***directory/filename.function***
+	 - The **function name** is the name of the final lambda function (and is set in ***serverless.yml***).
+	 - By default, the only file added to the current lambda function (That will show up on the console) is the handler file provided in the module name. If you would like to include other files in the final lambda function that is deployed, you may edit the newly generated ***serverless.yml*** and add the required files to the **functions/*your_function*/package/patterns**
+	 - You may also edit/add any other properties in ***serverless.yml***
+	 - Finally, the tool generates a buildspec.yml file for your function.
+		 - If you want to deploy all lambda functions present in ***serverless.yml*** you can press **'a'** in the final step. Otherwise, press **'n'**.
+
+%prep
+%autosetup -n slsmanager-0.2.2
+
+%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-slsmanager -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Wed May 31 2023 Python_Bot <Python_Bot@openeuler.org> - 0.2.2-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..f709777
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+336c7b4d7574f14c432c04d7ac741175  slsmanager-0.2.2.tar.gz