merge edc-ui

connector-ui/.browserslistrc

@@ -0,0 +1,17 @@
+# This file is used by the build system to adjust CSS and JS output to support the specified browsers below.
+# For additional information regarding the format and rule options, please see:
+# https://github.com/browserslist/browserslist#queries
+
+# For the full list of supported browsers by the Angular framework, please see:
+# https://angular.io/guide/browser-support
+
+# You can see what browsers were selected by your queries by running:
+#   npx browserslist
+
+last 1 Chrome version
+last 1 Firefox version
+last 2 Edge major versions
+last 2 Safari major versions
+last 2 iOS major versions
+Firefox ESR
+not IE 11 # Angular supports IE 11 only as an opt-in. To opt-in, remove the 'not' prefix on this line.

connector-ui/.dockerignore

@@ -0,0 +1,8 @@
+.idea
+.vscode
+misc
+openapi
+tmp
+node_modules
+src/assets/config/*.json
+.env*

connector-ui/.editorconfig

@@ -0,0 +1,17 @@
+# Editor configuration, see https://editorconfig.org
+root = true
+
+[*]
+charset = utf-8
+indent_style = space
+indent_size = 2
+insert_final_newline = true
+trim_trailing_whitespace = true
+end_of_line = lf
+
+[*.ts]
+quote_type = single
+
+[*.md]
+max_line_length = off
+trim_trailing_whitespace = false

connector-ui/.env.local-dev

@@ -0,0 +1,11 @@
+# .env file configured for default npm run start commands
+# see app-config-properties.ts for list of all configurable values
+EDC_UI_ACTIVE_PROFILE=sovity-open-source
+
+EDC_UI_USE_FAKE_BACKEND=true
+EDC_UI_MANAGEMENT_API_URL=http://edc.fake-backend
+EDC_UI_MANAGEMENT_API_KEY=no-api-key-required-in-local-dev
+EDC_UI_CATALOG_URLS=http://existing-other-connector/api/dsp,http://does-not-exist-but-is-super-long-so-we-can-test/api/dsp, http://how-wrapping-works-in-subtext-of-catalog-url-select/api/dsp
+EDC_UI_LOGOUT_URL=https://example.com/logout
+EDC_UI_CONNECTOR_ENDPOINT=http://localhost:3000/api/dsp
+EDC_UI_MANAGEMENT_API_URL_SHOWN_IN_DASHBOARD=http://localhost:3000/api/control/management

connector-ui/.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,62 @@
+name: Bug Report Template
+description: Report a bug to help us improve
+labels: ["kind/bug"]
+body:
+  - type: textarea
+    id: description
+    attributes:
+      label: Description - What happened? *
+      description: A clear and concise description of the bug.
+      placeholder: Tell us what you see!
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior *
+      description: A clear and concise description of what you expected to happen.
+      placeholder: Tell us what you expected!
+    validations:
+      required: true
+  - type: textarea
+    id: observed
+    attributes:
+      label: Observed Behavior *
+      description: A clear and concise description of what happened instead.
+      placeholder: Tell us what you observed!
+    validations:
+      required: true
+  - type: textarea
+    id: steps
+    attributes:
+      label: Steps to Reproduce
+      description: Steps to reproduce the behavior.
+      placeholder: Tell us how to reproduce the issue!
+    validations:
+      required: false
+  - type: textarea
+    id: context
+    attributes:
+      label: Context Information
+      description: Add any other context about the problem here.
+    validations:
+      required: false
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, so no need for backticks.
+      render: shell
+    validations:
+      required: false
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: If applicable, add screenshots or other information to help explain your problem.
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        <sup>_* These fields are mandatory, without filling them it is not possible to create the issue._</sup>

connector-ui/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: true

connector-ui/.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,30 @@
+---
+name: Documentation Update Request
+about: Create a report to help us improve our documentation
+title: ""
+labels: "task/documentation"
+assignees: ""
+---
+
+# Documentation Update Request
+
+## Description
+<!-- Provide a brief overview of the documentation update request. What section or topic needs to be updated? -->
+
+## Current Documentation
+<!--- Insert a link to the current documentation related to the topic. -->
+
+## Proposed Changes
+<!-- Describe the changes that need to be made. Be as specific as possible. -->
+
+## Justification
+<!-- Explain why these changes are necessary. Is there new information, outdated content, or improvements needed for clarity? -->
+
+## Additional Context
+<!-- Include any additional context, screenshots, examples, or references that might help in understanding the update request. -->
+
+## Deadline
+<!-- Set a deadline for completing the documentation update, if applicable. -->
+
+## Notes
+<!-- Any additional notes or instructions for the team regarding this documentation update request. -->

connector-ui/.github/ISSUE_TEMPLATE/epic_template.md

@@ -0,0 +1,46 @@
+---
+name: Epic
+about: Help us with new ideas
+title: ""
+labels: "kind/epic"
+assignees: ""
+---
+
+# Epic
+
+## Description
+<!-- Brief summary of what this Epic is, whether it's a larger project, goal, or user story. Describe the job to be done, which persona this Epic is mainly for, or if more multiple, break it down by user and job story. -->
+
+### Requirements
+<!-- Which requirements do you have to be fulfilled? -->
+<!-- Which security-related requirements must be satisfied? -->
+
+## Work Breakdown
+<!-- If you already know what needs to be done, plase add a tasklist. -->
+
+```[tasklist]
+### Stories
+- [ ] Create Stories which can be converted into issues
+```
+
+### Security Constraints
+<!-- Which constraints can be checked that must be covered by the work breakdown? -->
+- [ ] Final solution design has been challenged for security related topics
+
+## Initiative / goal
+<!-- Describe how this Epic impacts an initiative the business is working on. -->
+
+### Hypothesis
+<!-- What is your hypothesis on the success of this Epic? Describe how success will be measured and what leading indicators the team will have to know if success has been hit. -->
+
+## Acceptance criteria and must have scope
+<!-- Define what is a must-have for launch and in-scope (e.g. security-related tasks like successful pen-tests). Keep this section fluid and dynamic until you lock-in priority during planning. Please list your criteria below. -->
+
+## Stakeholders
+<!-- Describe who needs to be kept up-to-date about this Epic, included in discussions, or updated along the way. Stakeholders can be both in Product/Engineering, as well as other teams like Customer Success who might want to keep customers updated on the epic project. -->
+
+## Timeline
+<!-- What's the timeline for this Epic, what resources are needed, and what might potentially block this from hitting the projected end date. -->
+
+## Need for refinement
+<!-- Which questions are open? From whom do you need more input to fully specify the epic? -->

connector-ui/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,36 @@
+---
+name: Feature Request
+about: Help us with new features
+title: ""
+labels: "kind/enhancement"
+assignees: ""
+---
+
+# Feature Request
+
+## Description
+<!-- A clear and concise description of what the customer wants to happen. Example below. -->
+-   As a USER who PRECONDITIONS, I want to DO_THING, so I can ACCOMPLISH_GOAL.
+
+## Which Areas Would Be Affected?
+<!-- e.g., DPF, CI, build, transfer, etc. -->
+
+## Why Is the Feature Desired?
+<!-- Are there any requirements? -->
+
+## How does this tie into our current product?
+<!-- Describe whether this request is related to an existing workflow, feature, or otherwise something in the product today. Or, does this open us up to new markets and innovative ideas? -->
+
+## Stakeholders
+<!-- Add more on who asked for this, i.e. company, person, how much they pay us, what their tier is, are they a strategic account, etc. Who needs to be kept up-to-date about this feature? -->
+
+## Solution Proposal and Work Breakdown
+<!-- If you already know what needs to be done, please add a tasklist. -->
+
+```[tasklist]
+- [ ] Fix the GitHub Projects Labels, Sprint and other Metadata
+- [ ] Refine a Solution Proposal / Work Breakdown
+- [ ] (For Tech Team): Include acceptance criteria for the sub-tasks of the work breakdown
+- [ ] Add security related tasks and checks
+- [ ] Final solution design has been challenged for security related topics
+```

connector-ui/.github/ISSUE_TEMPLATE/process.md

@@ -0,0 +1,24 @@
+---
+name: Refine Process Request
+about: Existing processes must be adapted or new ones created
+title: ""
+labels: ["task/refine-process","task/documentation"]
+assignees: ""
+---
+
+# Process Refinement Request
+
+## Description
+<!-- Provide a brief description of the process that needs refinement and the reason behind it. -->
+
+## Current State
+<!-- Describe the current state of the process, including any pain points or inefficiencies. -->
+
+## Proposed Changes
+<!-- Outline the changes that need to be made to improve the process. Be as specific as possible. -->
+
+## Related Issues or PRs
+<!-- If there are any related issues or pull requests, mention them here. -->
+
+## Additional Information
+<!-- Any additional information or context that may be helpful for understanding the issue. -->

connector-ui/.github/ISSUE_TEMPLATE/release.md

@@ -0,0 +1,34 @@
+---
+name: Release
+about: Create an issue to track a release process.
+title: "Release x.y.z"
+labels: ["task/release", "scope/ce"]
+assignees: ""
+---
+
+# Release
+
+## Work Breakdown
+
+Feel free to edit this release checklist in-progress depending on what tasks need to be done:
+- [ ] Decide a release version depending on major/minor/patch changes in the CHANGELOG.md.
+- [ ] Update this issue's title to the new version
+- [ ] `release-prep` PR:
+  - [ ] Update the CHANGELOG.md.
+    - [ ] Check that all the entries have a link to an issue or a pull request.
+    - [ ] Add a clean `Unreleased` version.
+    - [ ] Add the version to the old section.
+    - [ ] Add the current date to the old version.
+    - [ ] Reorder, reword or combine changelog entries from a product perspective for consistency.
+    - [ ] Check the [Dependabot Alerts](https://github.com/sovity/edc-ui/security/dependabot) for anything fixable pre-release.
+    - [ ] Write or review a `Deployment Migration Notes` section.
+    - [ ] Write or review a release summary.
+    - [ ] Remove empty sections from the patch notes.
+  - [ ] Review the Screenshots in the Readme and update them if necessary.
+  - [ ] Merge the `release-prep` PR.
+- [ ] Wait for the main branch to be green.
+- [ ] Create a release and re-use the changelog section as release description, and the version as title.
+- [ ] Check if the pipeline built the release versions in the Actions-Section (or you won't see it).
+- [ ] Revisit the changed list of tasks and compare it with [.github/ISSUE_TEMPLATE/release.md](https://github.com/sovity/edc-ui/blob/main/.github/ISSUE_TEMPLATE/release.md). Propose changes where it
+  makes sense.
+- [ ] Close this issue.

connector-ui/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,10 @@
+_What issues does this PR close?_
+
+
+```[tasklist]
+### Checklist
+- [ ] The PR title is short and expressive.
+- [ ] I have updated the CHANGELOG.md and linked the changes to their issues. See [changelog_update.md](https://github.com/sovity/authority-portal/blob/main/docs/dev/changelog_updates.md) for more information.
+- [ ] I have updated the Deployment Migration Notes Section in the CHANGELOG.md for any configuration / external API changes.
+- [ ] I have performed a **self-review**
+```

connector-ui/.github/workflows/add_issue_to_project.yml

@@ -0,0 +1,17 @@
+name: Add issue to project action
+
+on:
+  issues:
+    types:
+      - opened
+
+jobs:
+  add_issue_to_project:
+    if: "!(startsWith(github.event.issue.title, '[Zammad Ticket') && github.event.issue.user.login == 'sovitybot')"
+    name: add_issue_to_project
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/[email protected]
+        with:
+          project-url: https://github.com/orgs/sovity/projects/9
+          github-token: ${{ secrets.ADD_ISSUE_TO_PROJECT_PAT }}

connector-ui/.github/workflows/automerge.yml

@@ -0,0 +1,18 @@
+name: auto-merge
+
+on:
+  pull_request:
+
+jobs:
+  automerge:
+    runs-on: ubuntu-latest
+    continue-on-error: true
+    permissions:
+      pull-requests: write
+      contents: write
+    steps:
+      - uses: fastify/github-action-merge-dependabot@v3
+        continue-on-error: true
+        with:
+          target: patch
+