https://github.com/entando/entando-plugin-sidecar

https://github.com/entando/entando-plugin-sidecar

Last synced: over 1 year ago
JSON representation

• Host: GitHub
• URL: https://github.com/entando/entando-plugin-sidecar
• Owner: entando
• License: lgpl-3.0
• Created: 2019-09-09T15:08:24.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2021-07-18T21:32:05.000Z (almost 5 years ago)
• Last Synced: 2025-02-01T03:27:49.999Z (over 1 year ago)
• Language: Java
• Size: 94.7 KB
• Stars: 0
• Watchers: 1
• Forks: 1
• Open Issues: 4
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Entando Plugin Sidecar

[![Build Status](https://jenkins.entandocloud.com/buildStatus/icon?job=de-entando-plugin-sidecar-master)](https://jenkins.entandocloud.com/job/de-entando-plugin-sidecar-master/)

[![Coverage Status](https://coveralls.io/repos/github/entando/entando-plugin-sidecar/badge.svg?branch=master)](https://coveralls.io/github/entando/entando-plugin-sidecar?branch=master)

This application is intended to be used as a sidecar for the Entando Plugins that need to manage connection

configurations and credentials (create, update, retrieve and delete). However, Entando Plugins don't need 

to call the endpoints directly. Instead, it will be done by the Connection Config Connector 

(https://github.com/entando/connection-config-connector).

The connection configurations and credentials managed by this application are stored as Kubernetes Secrets in a

Kubernetes Cluster.

## Running Integration tests

Integration tests require a Kubernetes environment. Having Minikube installed and configured is enough for this purpose.

Make sure a namespace is set up in your context. It can be done with the following command:

```bash

kubectl config set-context --current --namespace=default

```