v0.4.5

v0.4.5

Update dependencies and deprecate RAMv1

v0.4.5-rc01

v0.4.5-rc01

Update dependencies and deprecate

v0.4.4

v0.4.4

Steps to update

warning this version uses Cloud function runtime go116 that is preview at the time of this release

• update your go.mod:
  • update the require directive for github.com/BrunoReboul/ram to v0.4.4
• go mod tidy wil update the go.sum accordingly
• commit and push
• go build ram.go to complie the cli using this version
• git tag -l "ram-*-dev" to find what is your last tag version
• git tag -a ram-vA.B.C-dev -m "build: ram v0.4.4" where A,B,C depend on the result of the previous step
• git push --tags
• Wait for deployments in Cloud Build to complete
• ./ram -check -deploy -environment=dev -ramclisa=ramcli@<your_dev_pj_id>.iam.gserviceaccount.com regular deployment control
• Launch RAM Cloud Scheduler Jobs
• Check on the ram monitoring dashboard that the peak of cloud function activity is gone
• Check results in logs and reports

fixes

• Bug: Fix duplicate violations listgrroup #240

build

• github.com/open-policy-agent/opa from 0.33.1 to 0.34.2
• cloud.google.com/go/firestore from 1.6.0 to 1.6.1
• cloud.google.com/go/storage from 1.17.0 to 1.18.2
• google.golang.org/api from 0.58.0 to 0.60.0
• pubsub from 1.17.0 to 1.17.1

v0.4.4-rc01

fix listgroups duplicates

v0.4.3-rc01

v0.4.3-rc01

v0.4.2

v0.4.2

Steps to update

warning this version uses Cloud function runtime go116 that is preview at the time of this release

• update your go.mod:
  • replace go 1.13 by go 1.16
  • update the require directive for github.com/BrunoReboul/ram to v0.4.2
• commit and push
• go build ram.go to complie the cli using this version
• git tag -l "ram-*-dev" to find what is your last tag version
• git tag -a ram-vA.B.C-dev -m "build: ram v0.4.2" where A,B,C depend on the result of the previous step
• git push --tags
• Wait for deployments in Cloud Build to complete
• ./ram -check -deploy -environment=dev -ramclisa=ramcli@<your_dev_pj_id>.iam.gserviceaccount.com regular deployment control
• Launch RAM Cloud Scheduler Jobs
• Check on the ram monitoring dashboard that the peak of cloud function activity is gone
• Check results in logs and reports

fix

• fix: violation count is an index instead of a count #194
• fix: ramcli check deploy on setdashboard outputs false positives #224
• fix: ramcli remove manual action to select a monitoring workspace. no more required with metric scopes #225
• fix: Missing perm 'projects.topics.list' in custom role ram_monitor_deploy_core error on fresh install #227

feat

• utilities/glo/type_entry.go remove ref to pubsub, just triggering id to be agnostic (eventarc, pubsub etc)

build

Move to Cloud Function runtime go116 #220

• build: cloud.google.com/go v0.79.0 to v0.97
• build: cloud.google.com/go/bigquery v1.16.0 to v1.24.0
• cloud.google.com/go/firestore v1.5.0 to v1.6.0
• build: cloud.google.com/go/logging v1.3.0 to v1.4.2
• build: cloud.google.com/go/pubsub v1.10.1 to v1.17.0
• build: cloud.google.com/go/storage v1.14.0 to v1.17.0
• build: github.com/google/uuid v1.2.0 to v1.3.0
• build: github.com/open-policy-agent/opa v0.27.1 to v0.33.1
• build: golang.org/x/oauth2 v0.0.0-20210313182246-cd4f82c27b84 to v0.0.0-20210819190943-2bc19b11175f
• build: google.golang.org/api v0.42.0 to v0.58.0
• build: google.golang.org/genproto v0.0.0-20210312152112-fc591d9ea70f to v0.0.0-20210924002016-3dee208752a0

v0.4.2-rc16

ditto rc15

v0.4.2-rc15

fix missing topics.list permission

v0.4.2-rc14

fix ramcli -init, remove manual step 2 select a monitoring workspace. No more needed with metric scopes

v0.4.2-rc13

fix ramcli check deploy setdashboard false posivites