github repo upgrade

.github/CONTRIBUTING.md

@@ -0,0 +1,44 @@
+# Contributing
+
+Thank you for considering contributing to our repository! We welcome bug reports, feature requests, and contributions from the community.
+
+## Table of Contents
+
+- [Contributing](#contributing)
+  - [Table of Contents](#table-of-contents)
+  - [Security Vulnerabilities](#security-vulnerabilities)
+  - [Bug Reports and Feature Requests](#bug-reports-and-feature-requests)
+  - [How to Contribute](#how-to-contribute)
+  - [License](#license)
+
+## Security Vulnerabilities
+
+If you discover a security vulnerability, please follow our [SECURITY.md](SECURITY.md) and avoid creating public GitHub issues. Instead, report the issue privately.
+
+
+## Bug Reports and Feature Requests
+
+Please use GitHub issues to report bugs or suggest new features. Before submitting an issue, make sure to search for existing ones to avoid duplicates.
+
+- **Bug Reports:** Clearly describe the issue, including steps to reproduce it.
+- **Feature Requests:** Provide a detailed explanation of the requested feature.
+- **Context:** Any additional information of context
+
+
+## How to Contribute
+
+We appreciate your interest in contributing to the <reponame>. To contribute, follow these steps:
+
+1. Create a new issue on GitHub.
+2. Fork the repository.
+3. Create a new branch for your contribution: `git checkout -b feature/my-feature` or `git checkout -b bugfix/my-bugfix`.
+4. Make your changes.
+5. Test your changes to ensure they work as expected.
+6. Commit your changes: `git commit -m "Description of your changes"`.
+7. Push your changes to your fork: `git push origin feature/my-feature`.
+8. Open a pull request (PR) against the `main` branch of the main repository and link your created issue.
+
+
+## License
+
+By contributing to this repository, you agree that your contributions will be licensed under the [LICENSE](../LICENSE.md) used

.github/SECURITY.md

@@ -0,0 +1,7 @@
+# Security Policy
+
+## Reporting a Vulnerability
+If you discover a security vulnerability, please report it to us. We will respond to security incidents within 48 hours.
+
+- Contact: [dsh-platform@kpn.com]
+- Disclosure: We will work with you to ensure the vulnerability is disclosed responsibly.

CHANGELOG.md

@@ -0,0 +1,7 @@
+# Changelog
+
+## [v0.4.0] - 2022-11-23
+### Added
+- added IP san to CSR
+- update kafka client depedency
+- Bump dependency versions

CODEOWNERS

@@ -0,0 +1,4 @@
+# Code owners
+
+# The entire repository is owned by a team
+* @kpn-dsh/dsh-development

LICENSE.md

@@ -0,0 +1,7 @@
+Copyright 2024 KPN DSH 
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.