1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
|
%global _empty_manifest_terminate_build 0
Name: python-cloudrail-knowledge
Version: 0.0.228
Release: 1
Summary: Cloudrail's package for security rules
License: MIT License
URL: https://github.com/indeni/cloudrail-knowledge
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/de/44/08679a992c1fc0de51d71a4a2de2e5aad5cba8507c734dc50b11233977db/cloudrail-knowledge-0.0.228.tar.gz
BuildArch: noarch
Requires: python3-arnparse
Requires: python3-boto3
Requires: python3-netaddr
Requires: python3-dataclasses-json
Requires: python3-PyYAML
Requires: python3-packaging
Requires: python3-cfn-tools
Requires: python3-backoff
Requires: python3-requests
Requires: python3-deepdiff
Requires: python3-rsa
Requires: python3-natsort
Requires: python3-cfn-flip
%description
# Cloudrail Knowledge
[Cloudrail](https://www.indeni.com/cloudrail) is a tool for doing security analysis of infrastructure-as-code before
its deployment. For example Cloudrail can inspect Terraform plans and identify configurations
that violate company policy and best practices, and stop the CI pipeline accordingly.
This repository contains the rules that Cloudrail runs to conduct this analysis, as well as the context model the rules
evaluate against. You can use this repository for a few purposes:
1. Review the rules Cloudrail has and how they work.
2. Propose additions/changes to rules (just open a PR).
3. Build your own custom rules using the same context model existing rules use (for examples see
[cloudrail-sample-custom-rules](https://github.com/indeni/cloudrail-sample-custom-rules))
Want to understand how Cloudrail's knowledge works? Our documentation is available at
[https://knowledge.docs.cloudrail.app/](https://knowledge.docs.cloudrail.app/).
## Contributing
We welcome all contributions. Simply open an issue and a PR with your additions or changes. Some requirements:
* Branch names should be `<ticket-id>_<what_it's_trying_to_solve>`. Such as `issue_40_add_docdb_encryption_rule` or
`40_add_docdb_encryption_rule`.
* Any rule must have tests, see the `tests` directory on how these are built.
## Releases
This repository has frequent releases. Those with "beta" or "b" in their name are considered still in development,
not yet included in the production Cloudrail code (running in the Cloudrail SaaS). The latest non-beta release is
the one currently running within Cloudrail's production service.
%package -n python3-cloudrail-knowledge
Summary: Cloudrail's package for security rules
Provides: python-cloudrail-knowledge
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-cloudrail-knowledge
# Cloudrail Knowledge
[Cloudrail](https://www.indeni.com/cloudrail) is a tool for doing security analysis of infrastructure-as-code before
its deployment. For example Cloudrail can inspect Terraform plans and identify configurations
that violate company policy and best practices, and stop the CI pipeline accordingly.
This repository contains the rules that Cloudrail runs to conduct this analysis, as well as the context model the rules
evaluate against. You can use this repository for a few purposes:
1. Review the rules Cloudrail has and how they work.
2. Propose additions/changes to rules (just open a PR).
3. Build your own custom rules using the same context model existing rules use (for examples see
[cloudrail-sample-custom-rules](https://github.com/indeni/cloudrail-sample-custom-rules))
Want to understand how Cloudrail's knowledge works? Our documentation is available at
[https://knowledge.docs.cloudrail.app/](https://knowledge.docs.cloudrail.app/).
## Contributing
We welcome all contributions. Simply open an issue and a PR with your additions or changes. Some requirements:
* Branch names should be `<ticket-id>_<what_it's_trying_to_solve>`. Such as `issue_40_add_docdb_encryption_rule` or
`40_add_docdb_encryption_rule`.
* Any rule must have tests, see the `tests` directory on how these are built.
## Releases
This repository has frequent releases. Those with "beta" or "b" in their name are considered still in development,
not yet included in the production Cloudrail code (running in the Cloudrail SaaS). The latest non-beta release is
the one currently running within Cloudrail's production service.
%package help
Summary: Development documents and examples for cloudrail-knowledge
Provides: python3-cloudrail-knowledge-doc
%description help
# Cloudrail Knowledge
[Cloudrail](https://www.indeni.com/cloudrail) is a tool for doing security analysis of infrastructure-as-code before
its deployment. For example Cloudrail can inspect Terraform plans and identify configurations
that violate company policy and best practices, and stop the CI pipeline accordingly.
This repository contains the rules that Cloudrail runs to conduct this analysis, as well as the context model the rules
evaluate against. You can use this repository for a few purposes:
1. Review the rules Cloudrail has and how they work.
2. Propose additions/changes to rules (just open a PR).
3. Build your own custom rules using the same context model existing rules use (for examples see
[cloudrail-sample-custom-rules](https://github.com/indeni/cloudrail-sample-custom-rules))
Want to understand how Cloudrail's knowledge works? Our documentation is available at
[https://knowledge.docs.cloudrail.app/](https://knowledge.docs.cloudrail.app/).
## Contributing
We welcome all contributions. Simply open an issue and a PR with your additions or changes. Some requirements:
* Branch names should be `<ticket-id>_<what_it's_trying_to_solve>`. Such as `issue_40_add_docdb_encryption_rule` or
`40_add_docdb_encryption_rule`.
* Any rule must have tests, see the `tests` directory on how these are built.
## Releases
This repository has frequent releases. Those with "beta" or "b" in their name are considered still in development,
not yet included in the production Cloudrail code (running in the Cloudrail SaaS). The latest non-beta release is
the one currently running within Cloudrail's production service.
%prep
%autosetup -n cloudrail-knowledge-0.0.228
%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-cloudrail-knowledge -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Mon Apr 10 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.228-1
- Package Spec generated
|
