Skip to content

Commit 4030a9a

Browse files
paullatzelspergerpaullatzelsperger
committed
refactor: move AWS-specific code from other components here
1 parent 086bd51 commit 4030a9a

File tree

93 files changed

+9591
-1
lines changed

Some content is hidden

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

93 files changed

+9591
-1
lines changed

‎.github/ISSUE_TEMPLATE/adoption_request.md

+58
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,58 @@
1+
---
2+
name: Adoption Request
3+
about: Submit your feature to the project
4+
title: 'Adoption Request'
5+
labels: 'adoption'
6+
assignees: ''
7+
8+
---
9+
10+
# Adoption Request
11+
12+
_Thank you for wanting to contribute to the project! We are very happy to see the functionalities of the EDC being extended. Providing this open-source is a great opportunity for others with similar requirements and to avoid additional work._
13+
14+
_For any details about the guidelines for submitting features, please take a look at the [contribution categories](https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/main/contribution_categories.md)._
15+
16+
17+
## General information
18+
19+
Please provide some information about your project or code contribution.
20+
21+
_If you choose to be referenced as a "friend", these will be added to the [known friends list](https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/blob/main/known_friends.md)._
22+
_If you choose to add your feature as a core EDC component, links to your current code and correlated issues, discussions, and pull requests are of great importance._
23+
24+
| Title | Description | Contact | Links
25+
| :--- | :--- | :--- | :---
26+
| _My awesome project_ | _This is an example._ | _e-mail-address_ | _link to repository, homepage, discussion, etc._
27+
28+
29+
## Adoption level
30+
31+
Next, please tell us what level of adoption you intend to provide. _(pick only one)_
32+
33+
- [ ] Reference a feature as "friend"
34+
- [ ] Incorporate a feature as core EDC component
35+
36+
37+
38+
## Adoption in EDC core
39+
40+
_If you chose to add your feature as a core EDC component, please answer the following questions._
41+
42+
### Why should this contribution be adopted?
43+
_Please argue why this feature must be hosted upstream and be maintained by the EDC core team._
44+
45+
### Could it be achieved with existing functionality? If not, why?
46+
_If there is any existing code that can achieve the same thing with little modification, that is usually the preferable way for the EDC core team. We aim to keep the code succinct and want to avoid similar/duplicate code. Make sure you understand the EDC code base well!_
47+
48+
### Are there multiple use cases or applications who will benefit from the contribution?
49+
_Basically, we want you to motivate who will use that feature and why, thereby arguing the fact that it is well-suited to be adopted in the core code base. One-off features are better suited to be maintained externally._
50+
51+
### Can it be achieved without introducing third-party dependencies? If not, which ones?
52+
_EDC is a platform rather than an application, therefore we are extremely careful when it comes to introducing third party libraries. The reasons are diverse: security, license issues and over all JAR weight, just to mention a few important ones._
53+
54+
### Would this feature limit platform independence in any way? If so, how and why?
55+
_Features that do not work well in clustered environments are difficult to adopt, since EDC is designed from the ground up to be stateless and clusterable. Similarly, features, that have dependencies onto certain operating systems are difficult to argue._
56+
57+
### Is it going to be a self-contained feature, or would it cut across the entire code base?
58+
_Features that have a large impact on the code base are very complex to thoroughly test, they have a high chance to destabilize the code and require careful inspection. Self-contained features on the other hand are easier to isolate and test._

‎.github/ISSUE_TEMPLATE/bug_report.md

+39
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
name: Bug Report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: 'bug'
6+
assignees: ''
7+
8+
---
9+
10+
# Bug Report
11+
12+
## Describe the Bug
13+
_A clear and concise description of the bug._
14+
15+
### Expected Behavior
16+
_A clear and concise description of what you expected to happen._
17+
18+
### Observed Behavior
19+
_A clear and concise description of what happened instead._
20+
21+
## Steps to Reproduce
22+
Steps to reproduce the behavior:
23+
1. Go to '...'
24+
2. Click on '....'
25+
3. Scroll down to '....'
26+
4. See error
27+
28+
## Context Information
29+
_Add any other context about the problem here._
30+
31+
- Used version [e.g. EDC v1.0.0]
32+
- OS: [e.g. iOS, Windows]
33+
- ...
34+
35+
## Detailed Description
36+
_If applicable, add screenshots and logs to help explain your problem._
37+
38+
## Possible Implementation
39+
_You already know the root cause of the erroneous state and how to fix it? Feel free to share your thoughts._

‎.github/ISSUE_TEMPLATE/config.yml

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
---
2+
blank_issues_enabled: false
3+
contact_links:
4+
- name: Open up a blank issue
5+
url: https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/issues/new
6+
about: Don’t see your issue here? Open up a blank one
7+
- name: Ask a question or get support
8+
url: https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/discussions/categories/q-a
9+
about: Ask a question or request support for using the Eclipse Dataspace Connector
10+
- name: Take a look at the documentation
11+
url: https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/tree/main/docs
12+
about: Browse the documentation for more information

‎.github/ISSUE_TEMPLATE/feature_request.md

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
---
2+
name: Feature Request
3+
about: Help us with new ideas
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
# Feature Request
11+
12+
_If you are missing a feature or have an idea how to improve this project that should first be discussed, please feel free to open up a [discussion](https://github.com/eclipse-dataspaceconnector/DataSpaceConnector/discussions/categories/ideas)._
13+
14+
## Which Areas Would Be Affected?
15+
_e.g., DPF, CI, build, transfer, etc._
16+
17+
## Why Is the Feature Desired?
18+
_Are there any requirements?_
19+
20+
## Solution Proposal
21+
_If possible, provide a (brief!) solution proposal._

‎.github/PULL_REQUEST_TEMPLATE.md

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
## What this PR changes/adds
2+
3+
_Briefly describe WHAT your pr changes, which features it adds/modifies._
4+
5+
## Why it does that
6+
7+
_Briefly state why the change was necessary._
8+
9+
## Further notes
10+
11+
_List other areas of code that have changed but are not necessarily linked to the main feature. This could be method signature changes, package declarations, bugs that were encountered and were fixed inline, etc._
12+
13+
## Linked Issue(s)
14+
15+
Closes # <-- _insert Issue number if one exists_

‎.github/actions/bump-version/action.yml

+42
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
name: "Bump version in gradle.properties"
2+
description: "Increments the patch version of the version found in gradle.properties, appends -SNAPSHOT"
3+
inputs:
4+
target_branch:
5+
default: 'main'
6+
description: "Branch on which the version bump is to be done."
7+
required: false
8+
9+
runs:
10+
using: "composite"
11+
steps:
12+
- uses: actions/checkout@v3
13+
- name: read version from gradle.properties
14+
shell: bash
15+
run: |
16+
# Prepare git env
17+
git config user.name "eclipse-edc-bot"
18+
git config user.email "edc-bot@eclipse.org"
19+
20+
# checkout target
21+
git fetch origin
22+
git checkout ${{ inputs.target_branch }}
23+
24+
# determine current version
25+
oldVersion=$(grep "version" gradle.properties | awk -F= '{print $2}')
26+
27+
# read the major, minor, and patch components, consume -SNAPSHOT
28+
IFS=.- read -r RELEASE_VERSION_MAJOR RELEASE_VERSION_MINOR RELEASE_VERSION_PATCH SNAPSHOT<<<"$oldVersion"
29+
30+
# construct the new version
31+
newVersion="$RELEASE_VERSION_MAJOR.$RELEASE_VERSION_MINOR.$((RELEASE_VERSION_PATCH+1))"-SNAPSHOT
32+
33+
# replace every occurrence of =$oldVersion with =$newVersion
34+
grep -rlz "$oldVersion" . --exclude=\*.{sh,bin} | xargs sed -i "s/$oldVersion/$newVersion/g"
35+
36+
echo "Bumped the version from $oldVersion to $newVersion"
37+
38+
# Commit and push to the desired branch, defaults to 'main'
39+
git add .
40+
git commit --message "Bump version from $oldVersion to $newVersion [skip ci]"
41+
42+
git push origin ${{ inputs.target_branch }}

‎.github/actions/run-tests/action.yml

+21
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
name: "Run tests"
2+
description: "Run tests and archive test results for subsequent publication"
3+
inputs:
4+
command:
5+
required: true
6+
description: "The shell command to run tests"
7+
runs:
8+
using: "composite"
9+
steps:
10+
- name: Run Tests
11+
shell: bash
12+
run: ${{ inputs.command }}
13+
14+
- name: Upload Test Results
15+
uses: actions/upload-artifact@v3
16+
if: always()
17+
with:
18+
name: Test Results ${{ github.job }}
19+
path: |
20+
**/test-results/**/*.xml
21+
**/build/reports/jacoco/test/jacocoTestReport.xml

‎.github/actions/setup-build/action.yml

+12
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
name: "Setup Gradle"
2+
description: "Setup Gradle"
3+
runs:
4+
using: "composite"
5+
steps:
6+
- uses: actions/setup-java@v3
7+
with:
8+
java-version: '17'
9+
distribution: 'temurin'
10+
11+
- name: Setup Gradle cache
12+
uses: gradle/gradle-build-action@v2

‎.github/dependabot.yml

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
version: 2
2+
updates:
3+
# maintain dependencies for GitHub actions
4+
- package-ecosystem: "github-actions"
5+
directory: "/"
6+
schedule:
7+
interval: "weekly" # default = monday
8+
open-pull-requests-limit: 5
9+
labels:
10+
- "dependencies"
11+
- "github_actions"
12+
13+
# maintain dependencies for Gradle
14+
- package-ecosystem: "gradle" # checks build.gradle(.kts) and settings.gradle(.kts)
15+
directory: "/"
16+
schedule:
17+
interval: "daily"
18+
open-pull-requests-limit: 5
19+
labels:
20+
- "dependencies"
21+
- "java"
22+
ignore:
23+
- dependency-name: "org.eclipse.edc:edc-versions"
24+

‎.github/release.yaml

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
# This file determines how the auto-generated Release Notes in GitHub releases are structured.
2+
3+
changelog:
4+
exclude:
5+
labels:
6+
- no-changelog
7+
authors:
8+
- dependabot[bot]
9+
categories:
10+
- title: Bugfixes
11+
labels:
12+
- bug
13+
- title: New Features & Improvements
14+
labels:
15+
- "*"
16+
- title: Documentation
17+
labels:
18+
- documentation

‎.github/workflows/close-inactive-issues.yml

+67
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
name: Close Inactive Issues
2+
on:
3+
schedule:
4+
- cron: "30 1 * * *" # once a day (1:30 UTC)
5+
workflow_dispatch: # allow manual trigger
6+
7+
jobs:
8+
close-issues-with-assignee:
9+
runs-on: ubuntu-latest
10+
permissions:
11+
issues: write
12+
steps:
13+
- uses: actions/stale@v8
14+
with:
15+
operations-per-run: 1000
16+
days-before-issue-stale: 28
17+
days-before-issue-close: 7
18+
stale-issue-label: "stale"
19+
stale-issue-message: "This issue is stale because it has been open for 28 days with no activity."
20+
close-issue-message: "This issue was closed because it has been inactive for 7 days since being marked as stale."
21+
close-issue-reason: 'not_planned'
22+
days-before-pr-stale: -1 # ignore PRs (overwrite default days-before-stale)
23+
days-before-pr-close: -1 # ignore PRs (overwrite default days-before-close)
24+
remove-issue-stale-when-updated: true
25+
exempt-all-issue-milestones: true # issues with assigned milestones will be ignored
26+
exempt-issue-labels: bug # ignore issues labelled as bug
27+
repo-token: ${{ secrets.GITHUB_TOKEN }}
28+
29+
close-issues-without-assignee:
30+
runs-on: ubuntu-latest
31+
permissions:
32+
issues: write
33+
steps:
34+
- uses: actions/stale@v8
35+
with:
36+
operations-per-run: 1000
37+
days-before-issue-stale: 14
38+
days-before-issue-close: 7
39+
stale-issue-label: "stale"
40+
stale-issue-message: "This issue is stale because it has been open for 14 days with no activity."
41+
close-issue-message: "This issue was closed because it has been inactive for 7 days since being marked as stale."
42+
close-issue-reason: 'not_planned'
43+
days-before-pr-stale: -1 # ignore PRs (overwrite default days-before-stale)
44+
days-before-pr-close: -1 # ignore PRs (overwrite default days-before-close)
45+
remove-issue-stale-when-updated: true
46+
exempt-all-issue-milestones: true # issues with assigned milestones will be ignored
47+
exempt-all-issue-assignees: true # issues with assignees will be ignored
48+
exempt-issue-labels: bug # ignore issues labelled as bug
49+
repo-token: ${{ secrets.GITHUB_TOKEN }}
50+
51+
close-inactive-pull-requests:
52+
runs-on: ubuntu-latest
53+
permissions:
54+
pull-requests: write
55+
steps:
56+
- uses: actions/stale@v8
57+
with:
58+
operations-per-run: 1000
59+
days-before-issue-stale: -1 # ignore issues (overwrite default days-before-stale)
60+
days-before-issue-close: -1 # ignore issues (overwrite default days-before-close)
61+
stale-pr-label: "stale"
62+
stale-pr-message: "This pull request is stale because it has been open for 7 days with no activity."
63+
close-pr-message: "This pull request was closed because it has been inactive for 7 days since being marked as stale."
64+
days-before-pr-stale: 7
65+
days-before-pr-close: 7
66+
remove-pr-stale-when-updated: true
67+
repo-token: ${{ secrets.GITHUB_TOKEN }}

‎.github/workflows/codeql-analysis.yml

+50
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
name: "CodeQL"
2+
3+
on:
4+
push:
5+
branches-ignore:
6+
- 'dependabot/**'
7+
pull_request:
8+
branches: [ main ]
9+
paths-ignore:
10+
- '**.md'
11+
- 'docs/**'
12+
13+
concurrency:
14+
group: ${{ github.workflow }}-${{ github.ref }}
15+
cancel-in-progress: true
16+
17+
jobs:
18+
analyze:
19+
name: Analyze
20+
runs-on: ubuntu-latest
21+
22+
strategy:
23+
fail-fast: false
24+
matrix:
25+
language: [ 'java' ]
26+
# CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
27+
# Learn more:
28+
# https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
29+
30+
steps:
31+
- uses: actions/checkout@v3
32+
- uses: ./.github/actions/setup-build
33+
34+
# Initializes the CodeQL tools for scanning.
35+
- name: Initialize CodeQL
36+
uses: github/codeql-action/init@v2
37+
with:
38+
languages: ${{ matrix.language }}
39+
queries: +security-and-quality
40+
# If you wish to specify custom queries, you can do so here or in a config file.
41+
# By default, queries listed here will override any specified in a config file.
42+
# Prefix the list here with "+" to use these queries and those in the config file.
43+
# queries: ./path/to/local/query, your-org/your-repo/queries@main
44+
45+
# Compiles production Java source (without tests)
46+
- name: Build
47+
run: ./gradlew compileJava --no-daemon
48+
49+
- name: Perform CodeQL Analysis
50+
uses: github/codeql-action/analyze@v2

0 commit comments

Comments
 (0)