Skip to content

Releases: padok-team/burrito

v0.8.1

17 Sep 18:20
5b3f598
Compare
Choose a tag to compare

Changelog

Minor Features

Bug fixes

Dependency updates

v0.8.0

29 Aug 16:23
1d1fa0a
Compare
Choose a tag to compare
burrito-0 8

Changelog

💥 Breaking change

  • Burrito UI authentication: starting with 0.8.0 Burrito automatically adds authentication (defaults to HTTP Basic Auth) for its user interface. OIDC can also be configured.
    • To keep your Burrito instance public/un-authenticated you need to set config.burrito.server.basicAuth.enabled to false in your Helm values.

Features

Bug fixes

Others

v0.7.0

06 Jun 15:59
d7f4665
Compare
Choose a tag to compare

Changelog

Features

Bug fixes

Others

v0.6.5

28 Apr 08:39
d6aafd7
Compare
Choose a tag to compare

Changelog

Bug fix 💥

  • d6aafd7: fix(run-controller): client side filter for running pods list (#577) (@LucasMrqes)
    • The maxConcurrentRunnerPods feature was not functional since 0.6.4, this fix the bugs by doing pod filtering on Burrito side

Others

v0.6.4

22 Apr 10:10
7d022cf
Compare
Choose a tag to compare

Changelog

Features

Bug fixes

Dependency upgrades

v0.6.3

08 Apr 16:10
9a7b5cb
Compare
Choose a tag to compare

New features

  • SyncWindows allows you to define precise windows during which a layer will or will not be planned / applied by Burrito. Strongly inspired by Argo CD's SyncWindows. Documentation is available here.
  • MaxConcurrentRunnerPod setting can be set on the controller or repository level to limit the number of Burrito runner pods that run in parallel. More information in the associated documentation

These two features aim to empower Burrito users with tools to fine-tune the scheduling of operations, which can be especially useful for FinOps or safety-related considerations.

What's Changed

New Contributors

Full Changelog: v0.6.2...v0.6.3

v0.6.2

06 Mar 10:44
6c78042
Compare
Choose a tag to compare

What's Changed

  • chore(deps): update dependency vite to v6.0.9 [security] by @renovate in #517
  • chore(deps): update ui dependencies (minor) by @renovate in #493
  • chore(deps): update dependency eslint-config-prettier to v10 by @renovate in #494
  • fix(deps): update all patch dependencies (patch) by @renovate in #497
  • docs: update domain name to docs.burrito.tf by @corrieriluca in #524
  • feat(crd): support affinity in overriderunnerspec by @smeelock in #532
  • chore(deps): update codecov/codecov-action digest to 0565863 by @renovate in #519
  • chore(deps): update golangci/golangci-lint-action digest to 2226d7c by @renovate in #508
  • chore(deps): update actions/setup-go digest to f111f33 by @renovate in #518
  • chore(deps): update actions/cache digest to d4323d4 by @renovate in #533
  • chore(deps): update actions/setup-node digest to 1d0ff46 by @renovate in #526
  • docs: add affinity in available overrides by @corrieriluca in #538
  • fix(pullrequests): inherit all properties from original layer in pr layer by @LucasMrqes in #539

New Contributors

Full Changelog: v0.6.1...v0.6.2

v0.6.1

20 Jan 16:15
5eba278
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.6.0...v0.6.1

v0.6.0

16 Jan 16:35
3b38dc9
Compare
Choose a tag to compare

Important changes

Changes in Git provider authentication for PR/MR workflow

Prior to version v0.6.0, Burrito supported only one Git provider (either GitHub or GitLab) for enabling the PR/MR workflow. It means that if user were using multiple Git providers / organizations for the same Burrito installation, PR/MR workflow could apply to only one of them.

With version v0.6.0, the authentication for the PR/MR workflow relies on the secret associated to a TerraformRepository.

Deprecation warning: Old behavior with Git authentication configured in Burrito global config will remain functional until version 0.7.0.

To migrate to v0.6.0, add in each TerraformRepository secret the authentication mechanism (GitHub App / Token, GitLab Token) Burrito needs to use to track opened / closed Pull Requests.

Opt-in feature: sync repository with datastore

#467 introduces repository content syncing in the TerraformRepository controller (that was unused until now). For now this feature is disabled by default (this is done by disabling the TerraformRepository controller by default in Burrito's config) because Burrito runner does not get repository content from the datastore but still relies on Git clones.

In a future release Burrito runner pods will not clone Git repositories anymore and will instead fetch the last bundle from the datastore.

This will open the door to many enhancements in the few next releases such as layer auto-discovery in repos to name a few.

Changelog

Features

Bug fixes

Others

Read more

v0.5.1

15 Nov 16:59
7a895f7
Compare
Choose a tag to compare

Changelog

Features

Bug fixes

Others