This repository has been archived by the owner on Apr 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
feat: local deployment #117
Draft
revolunet
wants to merge
90
commits into
hasura
Choose a base branch
from
local
base: hasura
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Julien Bouquillon <[email protected]>
* feat(main): add talisman * fix(talisman): use scope: node
* init * fix: upgrade builtin keycloak-theme for docker-compose * wip * wip * wip * fix * test * fix: demo realm * fix * fix * fix * fix(keycloak): better logout * more roles * clean * kontinuous * fix * fix: rename app * fix * fix * docs: update * docs: update * fix keycloak service name * fix: migration * fix NEXT_PUBLIC_HASURA_GRAPHQL_ENDPOINT_URL * fix NEXT_PUBLIC_HASURA_GRAPHQL_ENDPOINT_URL * fix * seeds * seeds * seeds * add statefulsetAnnotations * add statefulsetAnnotations * add statefulsetAnnotations * add statefulsetAnnotations * add statefulsetAnnotations * add statefulsetAnnotations * add statefulsetAnnotations * dummy * fix seed pgSecretName * fix * fix * fix * fix precommit * debug * fix-ingress * fix: fix DSFR and next/link issues * fixlock * fix: icons * fix * Update .env.production * Update .env.staging * Update hasura.ts * fix code orga * fix: remixicon remove cdn * upgrade * fix: better docker-compose * Update README.md * Update ks-review.yaml * Update ks-review.yaml * Update ks-review.yaml * Update ks-review.yaml * doc: add talisman note * Update README.md * fix: add projectName * fix: rename to workflow-webhook.yaml Co-authored-by: Jo <[email protected]>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
4794696 | RSA Private Key | b5b7b89 | .kontinuous/env/local/templates/kubeconfig.yaml | View secret |
4794696 | RSA Private Key | f78fe7f | .kontinuous/env/local/templates/kubeconfig.yaml | View secret |
4798024 | RSA Private Key | f78fe7f | .kontinuous/env/local/templates/kubeconfig.yaml | View secret |
4798024 | RSA Private Key | 1dc17fe | .kontinuous/env/local/templates/kubeconfig.yaml | View secret |
4845101 | RSA Private Key | 1dc17fe | .kontinuous/env/local/templates/kubeconfig.yaml | View secret |
4845101 | RSA Private Key | 1dc17fe | .kontinuous/kind/kubeconfig.yaml | View secret |
4845101 | RSA Private Key | c6c21a5 | .kontinuous/env/local/templates/kubeconfig.yaml | View secret |
4845101 | RSA Private Key | c6c21a5 | .kontinuous/kind/kubeconfig.yaml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
Kudos, SonarCloud Quality Gate passed! |
🎉 Deployment for commit 57ff1e3 : IngressesDocker images
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ajout d'un env local de démo
Pourrait être utilisé pour des tests e2e aussi ?
Todo:
Instructions
Run
cd ./kontinuous/kind && ./setup-cluster.sh
to create a fresh kind clusterKontinuous adjustments for local deploy :
dependencies.fabrique.dependencies.contrib.validators.noPlainSecrets
tofalse
in.kontinuous/config.yaml
if you want to enable plain kube secrets (vs sealed-secrets)dev
env, create.kontinous/env/local
and adjustvalues.yaml
and templates if any. (ex: secrets)*.test
domains, install dnsmasq for .test domains on your local machine (example)run
kontinuous deploy --env local
withKUBECONFIG
pointing to your kind cluster kube config.