chore: release/v0.7.1 - Githubissues

GoogleCloudPlatform / cloud-ops-sandbox

Cloud Operations Sandbox is an open source collection of tools that helps practitioners to learn O11y and R9y practices from Google and apply them using Cloud Operations suite of tools.

Apache License 2.0

406 stars 148 forks source link

v0.7.1

Features

feat: add app version to GKE cluster (#788)

feat: Add config-based SRE Recipe Implementation (#826)

feat(terraform): add GKE location to TF apply (#811)

feat: renamed k8s containers to display service names (#819)

feat: recommendationservice crash recipe (#817)

Bug Fixes

fix: currencyservice errors (#818)

fix(terraform): Update provider version constraints (#820)

fix: fix manual website trigger

fix: removed extra trigger from website workflow

fix: update website workflows (#822)

fix: telemetry on develop branch (#823)

fix: Increase frontend pod resources (#810)

fix(describe): fix sandboxctl describe output format (#821)

fix: update outdated loadgen env variable in sandboxctl (#807)

Tests

tests: Add integration tests for validating SRE Recipe config schema (#836)

ci: fixed release script

ci: fix cloud build container workflow (#806)

Miscellaneous

chore: fixed make-release

chore: update website version number (#846)

chore: add policy documents (#843)

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

:memo: Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

What to do if you already signed the CLA

Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.