Skip to content

Commit 2bfd33a

Browse files
petrkalospetrkalos
committed
initial code
1 parent 63158c2 commit 2bfd33a

45 files changed

Lines changed: 63063 additions & 16 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.bumpversion.cfg‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
[bumpversion]
2+
current_version = 0.3.0a1
3+
commit = False
4+
tag = False
5+
tag_name = {new_version}
6+
parse = (?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)((?P<release>[a-z]+)(?P<build>\d+))?
7+
serialize =
8+
{major}.{minor}.{patch}{release}{build}
9+
{major}.{minor}.{patch}
10+
11+
[bumpversion:part:release]
12+
optional_value = rc
13+
values =
14+
a
15+
b
16+
rc
17+
18+
[bumpversion:part:build]
19+
first_value = 1
20+
21+
[bumpversion:file:pyproject.toml]

‎.github/ISSUE_TEMPLATE/bug_report.yml‎

Lines changed: 69 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,69 @@
1+
name: Bug report
2+
description: Create a report to help us improve.
3+
labels: "bug"
4+
5+
body:
6+
- type: textarea
7+
attributes:
8+
label: Describe the bug
9+
description: >-
10+
A clear and concise description of what the bug is.
11+
validations:
12+
required: true
13+
14+
- type: textarea
15+
attributes:
16+
label: How to Reproduce
17+
description: Steps to reproduce the behavior.
18+
value: |
19+
```
20+
*P.S. Please do not attach files as it's considered a security risk. Add code snippets directly in the message body as much as possible.*
21+
```
22+
validations:
23+
required: true
24+
25+
- type: textarea
26+
attributes:
27+
label: Expected behavior
28+
description: >-
29+
A clear and concise description of what you expected to happen.
30+
31+
- type: input
32+
attributes:
33+
label: Your project
34+
description: >-
35+
Link to your project.
36+
validations:
37+
required: false
38+
39+
- type: textarea
40+
attributes:
41+
label: Screenshots
42+
description: >-
43+
If applicable, add screenshots to help explain your problem.
44+
validations:
45+
required: false
46+
47+
- type: input
48+
attributes:
49+
label: OS
50+
description: >-
51+
[e.g. Unix/Linux/Mac/Win/other with version]
52+
validations:
53+
required: true
54+
- type: input
55+
attributes:
56+
label: Python version
57+
validations:
58+
required: true
59+
- type: input
60+
attributes:
61+
label: AWS data.all version
62+
validations:
63+
required: true
64+
- type: textarea
65+
attributes:
66+
label: Additional context
67+
description: >-
68+
Add any other context about the problem here.
69+
[e.g. URL or Ticket]

‎.github/ISSUE_TEMPLATE/enhancement-request.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Enhancement request
3+
about: Suggest an idea to enhance some existing feature
4+
title: ''
5+
labels: enhancement
6+
assignees: ''
7+
8+
---
9+
10+
**Is your idea related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
*P.S. Don't attach files. Please, prefer add code snippets directly in the message body.*

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: '<short description for the feature>'
5+
labels: feature
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.
21+
22+
*P.S. Please Don't attach files. Add code snippets directly in the message body instead.*

‎.github/ISSUE_TEMPLATE/question.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
name: Question
3+
about: Ask with as many useful details as possible
4+
title: ''
5+
labels: question
6+
assignees: ''
7+
8+
---
9+
10+
*P.S. Don't attach files. Please, prefer add code snippets directly in the message body.*

‎.github/ISSUE_TEMPLATE/support-dataall.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
name: Support AWS data.all
3+
about: Add your organisation's name or logo to the AWS data.all read.me
4+
title: "[Support AWS data.all]: <your organisation name>"
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
Thank you for letting us use your organisation's name on the AWS data.all read.me page and letting other customers know that you support the project! If you would like us to also display your organisation's logo. please raise a linked pull request to provide an image file for the logo.
11+
12+
Please add any files to *docs/source/_static/*
13+
14+
Organisation Name:
15+
Your Name:
16+
Your Position:
17+
I have included a logo: y/n
18+
19+
*By raising a Support AWS data.all issue (and related pull request), you are granting AWS permission to use your company’s name (and logo) for the limited purpose described here and you are confirming that you have authority to grant such permission.*

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
### Feature or Bugfix
2+
<!-- please choose -->
3+
- Feature
4+
- Bugfix
5+
- Refactoring
6+
7+
### Detail
8+
- <feature1 or bug1>
9+
- <feature2 or bug2>
10+
11+
### Relates
12+
- <URL or Ticket>
13+
14+
### Security
15+
Please answer the questions below briefly where applicable, or write `N/A`. Based on
16+
[OWASP 10](https://owasp.org/Top10/en/).
17+
18+
- Does this PR introduce or modify any input fields or queries - this includes
19+
fetching data from storage outside the application (e.g. a database, an S3 bucket)?
20+
- Is the input sanitized?
21+
- What precautions are you taking before deserializing the data you consume?
22+
- Is injection prevented by parametrizing queries?
23+
- Have you ensured no `eval` or similar functions are used?
24+
- Does this PR introduce any functionality or component that requires authorization?
25+
- How have you ensured it respects the existing AuthN/AuthZ mechanisms?
26+
- Are you logging failed auth attempts?
27+
- Are you using or adding any cryptographic features?
28+
- Do you use a standard proven implementations?
29+
- Are the used keys controlled by the customer? Where are they stored?
30+
- Are you introducing any new policies/roles/users?
31+
- Have you used the least-privilege principle? How?
32+
33+
34+
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

‎.github/dependabot.yml‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
version: 2
2+
updates:
3+
- package-ecosystem: "pip"
4+
directory: "/"
5+
schedule:
6+
interval: "weekly"
7+
time: "09:00"
8+
timezone: "Europe/London"
9+
groups:
10+
production-dependencies:
11+
dependency-type: "production"
12+
development-dependencies:
13+
dependency-type: "development"

‎.github/workflows/bandit.yml‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
name: Bandit
2+
3+
on:
4+
workflow_dispatch:
5+
push:
6+
branches:
7+
- main
8+
pull_request:
9+
branches:
10+
- main
11+
12+
permissions:
13+
contents: read
14+
15+
jobs:
16+
build:
17+
runs-on: ubuntu-latest
18+
steps:
19+
- uses: actions/checkout@v3
20+
- name: Set up Python ${{ matrix.python-version }}
21+
uses: actions/setup-python@v4
22+
with:
23+
python-version: ${{ matrix.python-version }}
24+
- name: Install
25+
run: |
26+
python -m pip install --upgrade pip
27+
python -m pip install bandit
28+
- name: Bandit
29+
run: bandit -r -lll -ii .

‎.github/workflows/git-hygiene.yml‎

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
name: "Close Stale Issues"
2+
3+
on:
4+
workflow_dispatch:
5+
schedule:
6+
- cron: "0 */3 * * *"
7+
8+
jobs:
9+
cleanup:
10+
permissions:
11+
issues: write
12+
pull-requests: write
13+
runs-on: ubuntu-latest
14+
name: Stale issue job
15+
steps:
16+
- uses: actions/stale@v4
17+
with:
18+
repo-token: ${{ secrets.GITHUB_TOKEN }}
19+
days-before-stale: 60
20+
days-before-close: 7
21+
exempt-issue-labels: 'needs-triage,help wanted,backlog'
22+
exempt-pr-labels: 'needs-triage'
23+
stale-issue-label: 'closing-soon'
24+
operations-per-run: 100
25+
enable-statistics: true
26+
stale-issue-message: |
27+
Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed.
28+
stale-pr-label: 'closing-soon'
29+
stale-pr-message: |
30+
Marking this pull request as stale due to inactivity. This helps our maintainers find and focus on the active pull requests.
31+
debug-only: false
32+
ascending: true
33+
exempt-all-milestones: true
34+
exempt-all-assignees: true

0 commit comments

Comments
 (0)