summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCoprDistGit <infra@openeuler.org>2023-04-11 10:36:12 +0000
committerCoprDistGit <infra@openeuler.org>2023-04-11 10:36:12 +0000
commit10e24d37367b102a5509db1b7e84dce8828e3345 (patch)
tree6d19c51f062ce374464a1b88dcf5dd3e3821ff05
parentcd8b1e057c78960b9268fae2bbff6937342459b9 (diff)
automatic import of python-cdk-gitlab
-rw-r--r--.gitignore1
-rw-r--r--python-cdk-gitlab.spec284
-rw-r--r--sources1
3 files changed, 286 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index e69de29..db8d267 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/cdk-gitlab-2.0.241.tar.gz
diff --git a/python-cdk-gitlab.spec b/python-cdk-gitlab.spec
new file mode 100644
index 0000000..06ad515
--- /dev/null
+++ b/python-cdk-gitlab.spec
@@ -0,0 +1,284 @@
+%global _empty_manifest_terminate_build 0
+Name: python-cdk-gitlab
+Version: 2.0.241
+Release: 1
+Summary: High level CDK construct to provision GitLab integrations with AWS
+License: Apache-2.0
+URL: https://github.com/pahud/cdk-gitlab.git
+Source0: https://mirrors.nju.edu.cn/pypi/web/packages/ae/11/e0ee7c01b1296309004f1dda9442fe32c0453659b90ddb17a92bd2368dfd/cdk-gitlab-2.0.241.tar.gz
+BuildArch: noarch
+
+Requires: python3-aws-cdk-lib
+Requires: python3-constructs
+Requires: python3-jsii
+Requires: python3-publication
+Requires: python3-typeguard
+
+%description
+[![NPM version](https://badge.fury.io/js/cdk-gitlab.svg)](https://badge.fury.io/js/cdk-gitlab)
+[![PyPI version](https://badge.fury.io/py/cdk-gitlab.svg)](https://badge.fury.io/py/cdk-gitlab)
+[![release](https://github.com/pahud/cdk-gitlab/actions/workflows/release.yml/badge.svg)](https://github.com/pahud/cdk-gitlab/actions/workflows/release.yml)
+
+# cdk-gitlab
+
+High level CDK construct to provision GitLab integrations with AWS
+
+# Install
+
+Use the npm dist tag to opt in CDKv1 or CDKv2:
+
+```sh
+// for CDKv2
+npm install cdk-gitlab
+or
+npm install cdk-gitlab@latest
+
+// for CDKv1
+npm install cdk-gitlab@cdkv1
+```
+
+# Sample
+
+```python
+import { Provider, FargateJobExecutor, FargateRunner, JobExecutorImage } from 'cdk-gitlab';
+
+const provider = new Provider(stack, 'GitlabProvider', { vpc });
+
+// create a Amazon EKS cluster
+provider.createFargateEksCluster(stack, 'GitlabEksCluster', {
+ clusterOptions: {
+ vpc,
+ version: eks.KubernetesVersion.V1_19,
+ },
+});
+
+// create a default fargate runner with its job executor
+provider.createFargateRunner();
+
+// alternatively, create the runner and the executor indivicually.
+// first, create the executor
+const executor = new FargateJobExecutor(stack, 'JobExecutor', {
+ image: JobExecutorImage.DEBIAN,
+});
+
+// second, create the runner with the task definition of the executor
+new FargateRunner(stack, 'FargateRunner', {
+ vpc,
+ executor,
+});
+
+// TBD - create Amazon EC2 runner for the GitLab
+provider.createEc2Runner(...);
+
+});
+```
+
+# Fargate Runner with Amazon ECS
+
+On deployment with `createFargateRunner()`, the **Fargate Runner** will be provisioned in Amazon ECS with AWS Fargate and [Amazon ECS Capacity Providers](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html). By default, the `FARGATE` and `FARGATE_SPOT` capacity providers are available for the Amazon ECS cluster and the runner and job executor will run on `FARGATE_SPOT`. You can specify your custom `clusterDefaultCapacityProviderStrategy` and `serviceDefaultCapacityProviderStrategy` properties from the `FargateRunner` construct for different capacity provider strategies.
+
+# Deploy
+
+```sh
+cdk deploy -c GITLAB_REGISTRATION_TOKEN=<TOKEN>
+```
+
+
+
+
+%package -n python3-cdk-gitlab
+Summary: High level CDK construct to provision GitLab integrations with AWS
+Provides: python-cdk-gitlab
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-cdk-gitlab
+[![NPM version](https://badge.fury.io/js/cdk-gitlab.svg)](https://badge.fury.io/js/cdk-gitlab)
+[![PyPI version](https://badge.fury.io/py/cdk-gitlab.svg)](https://badge.fury.io/py/cdk-gitlab)
+[![release](https://github.com/pahud/cdk-gitlab/actions/workflows/release.yml/badge.svg)](https://github.com/pahud/cdk-gitlab/actions/workflows/release.yml)
+
+# cdk-gitlab
+
+High level CDK construct to provision GitLab integrations with AWS
+
+# Install
+
+Use the npm dist tag to opt in CDKv1 or CDKv2:
+
+```sh
+// for CDKv2
+npm install cdk-gitlab
+or
+npm install cdk-gitlab@latest
+
+// for CDKv1
+npm install cdk-gitlab@cdkv1
+```
+
+# Sample
+
+```python
+import { Provider, FargateJobExecutor, FargateRunner, JobExecutorImage } from 'cdk-gitlab';
+
+const provider = new Provider(stack, 'GitlabProvider', { vpc });
+
+// create a Amazon EKS cluster
+provider.createFargateEksCluster(stack, 'GitlabEksCluster', {
+ clusterOptions: {
+ vpc,
+ version: eks.KubernetesVersion.V1_19,
+ },
+});
+
+// create a default fargate runner with its job executor
+provider.createFargateRunner();
+
+// alternatively, create the runner and the executor indivicually.
+// first, create the executor
+const executor = new FargateJobExecutor(stack, 'JobExecutor', {
+ image: JobExecutorImage.DEBIAN,
+});
+
+// second, create the runner with the task definition of the executor
+new FargateRunner(stack, 'FargateRunner', {
+ vpc,
+ executor,
+});
+
+// TBD - create Amazon EC2 runner for the GitLab
+provider.createEc2Runner(...);
+
+});
+```
+
+# Fargate Runner with Amazon ECS
+
+On deployment with `createFargateRunner()`, the **Fargate Runner** will be provisioned in Amazon ECS with AWS Fargate and [Amazon ECS Capacity Providers](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html). By default, the `FARGATE` and `FARGATE_SPOT` capacity providers are available for the Amazon ECS cluster and the runner and job executor will run on `FARGATE_SPOT`. You can specify your custom `clusterDefaultCapacityProviderStrategy` and `serviceDefaultCapacityProviderStrategy` properties from the `FargateRunner` construct for different capacity provider strategies.
+
+# Deploy
+
+```sh
+cdk deploy -c GITLAB_REGISTRATION_TOKEN=<TOKEN>
+```
+
+
+
+
+%package help
+Summary: Development documents and examples for cdk-gitlab
+Provides: python3-cdk-gitlab-doc
+%description help
+[![NPM version](https://badge.fury.io/js/cdk-gitlab.svg)](https://badge.fury.io/js/cdk-gitlab)
+[![PyPI version](https://badge.fury.io/py/cdk-gitlab.svg)](https://badge.fury.io/py/cdk-gitlab)
+[![release](https://github.com/pahud/cdk-gitlab/actions/workflows/release.yml/badge.svg)](https://github.com/pahud/cdk-gitlab/actions/workflows/release.yml)
+
+# cdk-gitlab
+
+High level CDK construct to provision GitLab integrations with AWS
+
+# Install
+
+Use the npm dist tag to opt in CDKv1 or CDKv2:
+
+```sh
+// for CDKv2
+npm install cdk-gitlab
+or
+npm install cdk-gitlab@latest
+
+// for CDKv1
+npm install cdk-gitlab@cdkv1
+```
+
+# Sample
+
+```python
+import { Provider, FargateJobExecutor, FargateRunner, JobExecutorImage } from 'cdk-gitlab';
+
+const provider = new Provider(stack, 'GitlabProvider', { vpc });
+
+// create a Amazon EKS cluster
+provider.createFargateEksCluster(stack, 'GitlabEksCluster', {
+ clusterOptions: {
+ vpc,
+ version: eks.KubernetesVersion.V1_19,
+ },
+});
+
+// create a default fargate runner with its job executor
+provider.createFargateRunner();
+
+// alternatively, create the runner and the executor indivicually.
+// first, create the executor
+const executor = new FargateJobExecutor(stack, 'JobExecutor', {
+ image: JobExecutorImage.DEBIAN,
+});
+
+// second, create the runner with the task definition of the executor
+new FargateRunner(stack, 'FargateRunner', {
+ vpc,
+ executor,
+});
+
+// TBD - create Amazon EC2 runner for the GitLab
+provider.createEc2Runner(...);
+
+});
+```
+
+# Fargate Runner with Amazon ECS
+
+On deployment with `createFargateRunner()`, the **Fargate Runner** will be provisioned in Amazon ECS with AWS Fargate and [Amazon ECS Capacity Providers](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/cluster-capacity-providers.html). By default, the `FARGATE` and `FARGATE_SPOT` capacity providers are available for the Amazon ECS cluster and the runner and job executor will run on `FARGATE_SPOT`. You can specify your custom `clusterDefaultCapacityProviderStrategy` and `serviceDefaultCapacityProviderStrategy` properties from the `FargateRunner` construct for different capacity provider strategies.
+
+# Deploy
+
+```sh
+cdk deploy -c GITLAB_REGISTRATION_TOKEN=<TOKEN>
+```
+
+
+
+
+%prep
+%autosetup -n cdk-gitlab-2.0.241
+
+%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-cdk-gitlab -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 2.0.241-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..1dd19fc
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+a9aee1eaff5901ddac224e2abbfb2b62 cdk-gitlab-2.0.241.tar.gz