Tags: sofam/clouddriver
Tags
fix(plugins): add an option for strict plugin loading (spinnaker#4485)
fix(saga): Remove import of EventSourceAutoConfiguration on SagaAutoC… …onfiguration (spinnaker#4477)
chore(dependencies): Autobump korkVersion (spinnaker#4474) Co-authored-by: runner <runner@fv-az51.internal.cloudapp.net>
fix(core): Only log relevant details of description (spinnaker#4456) (s… …pinnaker#4457) When we encounter a description that should have application restrictions but doesn't, we log a warning including the full description JSON. In some cases (ex: Kubernetes) this description may contain sensitive information that ideally wouldn't be logged. Ideally really sensitive values would come from artifacts so they aren't in the pipeline JSON at all, but let's nonetheless cut back on how much we are logging here to reduce the chance of sensitive information ending up in the logs. In particular, it's not clear how much the full description would help in debugging, as generally what is important is the class of the description (to check whether it implements ApplicationNameable or ResourcesNameable) and and the account, both of which will still be logged after this change. Co-authored-by: Eric Zimanyi <ezimanyi@google.com>
fix(core): Only log relevant details of description (spinnaker#4456) (s… …pinnaker#4458) When we encounter a description that should have application restrictions but doesn't, we log a warning including the full description JSON. In some cases (ex: Kubernetes) this description may contain sensitive information that ideally wouldn't be logged. Ideally really sensitive values would come from artifacts so they aren't in the pipeline JSON at all, but let's nonetheless cut back on how much we are logging here to reduce the chance of sensitive information ending up in the logs. In particular, it's not clear how much the full description would help in debugging, as generally what is important is the class of the description (to check whether it implements ApplicationNameable or ResourcesNameable) and and the account, both of which will still be logged after this change. Co-authored-by: Eric Zimanyi <ezimanyi@google.com>
fix(core): Only log relevant details of description (spinnaker#4456) (s… …pinnaker#4459) When we encounter a description that should have application restrictions but doesn't, we log a warning including the full description JSON. In some cases (ex: Kubernetes) this description may contain sensitive information that ideally wouldn't be logged. Ideally really sensitive values would come from artifacts so they aren't in the pipeline JSON at all, but let's nonetheless cut back on how much we are logging here to reduce the chance of sensitive information ending up in the logs. In particular, it's not clear how much the full description would help in debugging, as generally what is important is the class of the description (to check whether it implements ApplicationNameable or ResourcesNameable) and and the account, both of which will still be logged after this change. Co-authored-by: Eric Zimanyi <ezimanyi@google.com>
fix(sql): Cherry pick jooq changes (spinnaker#4435) * fix(sql): Cherry pick work * fix(tests): Fixed broken sql tests per PR spinnaker#4453 Co-authored-by: Mark Vulfson <mvulfson@netflix.com>
fix(kubernetes/v1): Don't pass force flag to patch operation (spinnak… …er#4449) (spinnaker#4450) The patchNamespacedStatefulSet is passing force=false; the Kubernetes API server doesn't allow this flag to be present at all for non-apply patch operations, which is causing a server-side failure. This only breaks on clusters >=1.14 as the flag was not present before. (I'm not sure if the client library was detecting the old version of the cluster and removing the flag before calling the API, or if the API was just ignoring the unknown flag, but either way the flag had no effect.) Co-authored-by: Eric Zimanyi <ezimanyi@google.com>
chore(dependencies): bump korkVersion and kotlinVersion (spinnaker#4447)
PreviousNext