anchialas

I had a bit of trouble figuring out how to use bitnami's sealed secrets with helm

Here's a definition of done to help you see what I was trying to achieve.

Definition of done

• Single secret available for a release in a namespace, listing all secret variables
• Regular helm workflow, with no extra kubeseal commands for developers
• Encrypted secrets clearly visible in git
• Sealedsecret managed by helm

anchialas

#!/bin/bash
# Sometimes you need to move your existing git repository
# to a new remote repository (/new remote origin).
# Here are a simple and quick steps that does exactly this.
#
# Let's assume we call "old repo" the repository you wish
# to move, and "new repo" the one you wish to move to.
#
### Step 1. Make sure you have a local copy of all "old repo"
### branches and tags.

anchialas

import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;

@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.FIELD)
public @interface EsId {

}

anchialas

# Check if today is Sunday, if commit is not a pull request, if git repo is official, and if branch is master. If checks pass, run Sonar reports
- "[[ $(date +%u) -gt 5 ]] && [[ $TRAVIS_PULL_REQUEST == false ]] && [[ $TRAVIS_REPO_SLUG == RepoOrg/RepoName ]] && [[ $TRAVIS_BRANCH == master ]] && mvn sonar:sonar"