Skip to content
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.

fix(deps): update dependency @socialgouv/kosko-charts to v9 #505

Merged
merged 2 commits into from
Jul 29, 2021

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 29, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@socialgouv/kosko-charts ^8.0.3 -> ^9.0.0 age adoption passing confidence

Release Notes

SocialGouv/kosko-charts

v9.0.0

Compare Source

BREAKING CHANGES
  • Our create database component is now creating one database per branch

Previously our @socialgouv/kosko-charts/components/azure-pg component was creating one database per commit. As it happen to be a rare need at @​SocialGouv, we now switch to one database per branch.

  • Unify commen pg.ts component use under the same function

Previously our @socialgouv/kosko-charts/components/azure-pg component was only handling the "dev"/"review" use case where we have to create the database and the user ourself. This ends up putting on the user land the responsibility of manually loading a sealedsecret in other case. As it happen to be a common need at @​SocialGouv, we now deal with loading the file our creating the database as before if the named file does not exist.

import env from "@​kosko/env";
-import type { SealedSecret } from "@​kubernetes-models/sealed-secrets/bitnami.com/v1alpha1/SealedSecret";
 import { create } from "@​socialgouv/kosko-charts/components/azure-pg";
-import environments from "@​socialgouv/kosko-charts/environments";
-import { loadYaml } from "@​socialgouv/kosko-charts/utils/getEnvironmentComponent";
-import { updateMetadata } from "@​socialgouv/kosko-charts/utils/updateMetadata";

+export default create("pg-user", {
+  env,
+});
-export default async (): Promise<{ kind: string }[]> => {
-  if (env.env === "dev") {
-    return create({
-      env,
-    });
-  }
-
-  // in prod/preprod, we try to add a fixed sealed-secret
-  const secret = await loadYaml<SealedSecret>(
-    env,
-    `pg-user.sealed-secret.yaml`
-  );
-  if (!secret) {
-    return [];
-  }
-
-  const envParams = environments(process.env);
-  // add gitlab annotations
-  updateMetadata(secret, {
-    annotations: envParams.metadata.annotations ?? {},
-    labels: envParams.metadata.labels ?? {},
-    namespace: envParams.metadata.namespace,
-  });
-  return [secret];
-};

The new create function of @socialgouv/kosko-charts/components/azure-pg takes a name as fist argument used to "guest" the file to load ${name}.sealed-secret.yaml is the given env (as before)

v8.1.1

Compare Source

Bug Fixes
  • environments: github branch env slug missing prefix (#​623) (23fa233)

v8.1.0

Compare Source

Features

8.0.3 (2021-07-24)

Bug Fixes
Reverts

8.0.2 (2021-07-16)

Bug Fixes
  • ingress: missing pathType and name port collision (#​608) (9a12a7b)

8.0.1 (2021-07-15)

Bug Fixes

Configuration

📅 Schedule: "before 3am on the first day of the month" in timezone Europe/Paris.

🚦 Automerge: Enabled.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@douglasduteil douglasduteil merged commit 944dddd into master Jul 29, 2021
@douglasduteil douglasduteil deleted the renovate/major-kosko-monorepo branch July 29, 2021 19:10
SocialGroovyBot added a commit that referenced this pull request Jul 29, 2021
## [3.0.8](v3.0.7...v3.0.8) (2021-07-29)

### Bug Fixes

* **deps:** update dependency @socialgouv/kosko-charts to v9 ([#505](#505)) ([944dddd](944dddd))
@SocialGroovyBot
Copy link
Member

🎉 This PR is included in version 3.0.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants