Terraform Incompatible API version with plugin. Plugin version: 5, Core version: 4 - plugins

Running into this module error no one on my team, which is all new, does not know. Below is my terraform version. And yes, I know terraform 0.11 is old as hell but I was just hired and have to fix this.
$ terraform --version
Terraform v0.11.14
provider.aws v2.70.0
provider.grafana v1.10.0
provider.kubernetes v1.8.0
provider.null v2.1.2
provider.postgresql v1.7.2
provider.random v2.3.1
Error:
Error: Error asking for user input: 1 error occurred:
* module.editedout-dev-keycloak.provider.grafana: Incompatible API version with plugin. Plugin version: 5, Core version: 4

As described in the documented requirements for the Grafana provider version 1.10, the minimum core version of Terraform for that version of the provider is 0.12. The reason for this can be seen referenced in the CHANGELOG with issue 159. The provider upgraded to version 2 of the provider SDK, which enforces core Terraform at minimum version 0.12. More details around that minimum version bump can be read in that issue description.
If you want to move forward, then you would need to lock in the Grafana provider to version 1.9.0. In Terraform version 0.11, you would achieve that with the following declarative syntax in a config file for the root module config, or preferably in the module declared as editedout-dev-keycloak in the error message you displayed:
provider "grafana" {
version = "1.9.0"
}

Related

dj-stripe referencing a non-existent migration

I have a django model where I have a OneToOneField to djstripe's Customer. When I run makemigrations a migration is created with the following dependency:
dependencies = [ ('djstripe', '0011_alter_invoice_charge_alter_invoice_customer_and_more'), ('users', '0007_rename_username), ]
Everything seems to be okay locally, but then when I deploy my code it fails with the following error:
django.db.migrations.exceptions.NodeNotFoundError: Migration users.0008_stripecustomer dependencies reference nonexistent parent node ('djstripe', '0011_alter_invoice_charge_alter_invoice_customer_and_more')
Our pipeline does not run makemigrations, only migrate, so this seems a little weird that a djstripe migration is created when I run makemigrations locally but then I cannot use it in deployment. Plus, such migration does not exist in djstripe GitHub repository.
dj-stripe version: 2.6.1
Python version: 3.9
Django version: 4.0.1
Stripe API version: 2.68.0
Database type and version: postgres 12.9
It's an known bug in v. 4 - https://github.com/dj-stripe/dj-stripe/issues/1649#issuecomment-1117774629
To solve it you'd have to downgrade django to 3.x.x. They should fix it in the next update as well.

Sentry version incompatibility

Sentry latest version is incompatible with http plugin and if another version of sentry is used then it is also not compatible with rest of the other already used packages in project.
Even without version I tried to get its compatible version but this also not worked.
This is because Sentry uses http: ^0.13.0 because that's the earliest version which is null safe. The user uses a pretty outdated version of http.
Got the reply from GitHub: https://github.com/getsentry/sentry-dart/issues/694

What is the purpose of attribute keywords in Helm Chart's Chart.yaml?

I have seen in many Helm Chart's Chart.yaml where developers provide keywords, as for example
keywords:
- "http"
- "https"
- "web server"
What is the significance of providing these? Are these getting validated by something in Helm?
I tried to look out for reasons, but I did not get useful information, so posting here.
The keywords field specifies a list of keywords about the project. It helps user search charts based on keywords. For example, helm search repo database will bring up the charts which contain the database keyword such as postgres, mariadb, etc.
Search by keyword:
$ helm search repo database
NAME CHART VERSION APP VERSION DESCRIPTION
stable/cockroachdb 3.0.8 19.2.5 DEPRECATED -- CockroachDB is a scalable, surviv...
stable/couchdb 2.3.0 2.3.1 DEPRECATED A database featuring seamless multi-...
stable/dokuwiki 6.0.11 0.20180422.201901061035 DEPRECATED DokuWiki is a standards-compliant, s...
stable/ignite 1.2.2 2.7.6 DEPRECATED - Apache Ignite is an open-source di...
stable/janusgraph 0.2.6 1.0 DEPRECATED - Open source, scalable graph database.
stable/kubedb 0.1.3 0.8.0-beta.2 DEPRECATED KubeDB by AppsCode - Making running ...
stable/mariadb 7.3.14 10.3.22 DEPRECATED Fast, reliable, scalable, and easy t...
stable/mediawiki 9.1.9 1.34.0 DEPRECATED Extremely powerful, scalable softwar...
stable/mongodb 7.8.10 4.2.4 DEPRECATED NoSQL document-oriented database tha...
stable/mongodb-replicaset 3.17.2 3.6 DEPRECATED - NoSQL document-oriented database t...
stable/mysql 1.6.9 5.7.30 DEPRECATED - Fast, reliable, scalable, and easy...
stable/mysqldump 2.6.2 2.4.1 DEPRECATED! - A Helm chart to help backup MySQL...
stable/neo4j 3.0.1 4.0.4 DEPRECATED Neo4j is the world's leading graph d...
stable/pgadmin 1.2.2 4.18.0 pgAdmin is a web based administration tool for ...
stable/postgresql 8.6.4 11.7.0 DEPRECATED Chart for PostgreSQL, an object-rela...
stable/prisma 1.2.4 1.29.1 DEPRECATED Prisma turns your database into a re...
stable/prometheus 11.12.1 2.20.1 DEPRECATED Prometheus is a monitoring system an...
stable/rethinkdb 1.1.4 0.1.0 DEPRECATED - The open-source database for the r...
stable/couchbase-operator 1.0.4 1.2.2 DEPRECATED A Helm chart to deploy the Couchbase...
stable/hazelcast 3.3.2 4.0.1 DEPRECATED Hazelcast IMDG is the most widely us...
stable/influxdb 4.3.2 1.7.9 DEPRECATED Scalable datastore for metrics, even...
stable/percona 1.2.3 5.7.26 DEPRECATED - free, fully compatible, enhanced, ...
stable/percona-xtradb-cluster 1.0.8 5.7.19 DEPRECATED - free, fully compatible, enhanced, ...
stable/redis 10.5.7 5.0.7 DEPRECATED Open source, advanced key-value stor...
stable/redis-ha 4.4.6 5.0.6 DEPRECATED - Highly available Kubernetes implem...
Check whether the chart has that keyword:
$ helm show chart stable/mariadb
apiVersion: v1
appVersion: 10.3.22
deprecated: true
description: DEPRECATED Fast, reliable, scalable, and easy to use open-source relational database system. MariaDB Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software. Highly available MariaDB cluster.
home: https://mariadb.org
icon: https://bitnami.com/assets/stacks/mariadb/img/mariadb-stack-220x234.png
keywords:
- mariadb
- mysql
- database
- sql
- prometheus
name: mariadb
sources:
- https://github.com/bitnami/bitnami-docker-mariadb
- https://github.com/prometheus/mysqld_exporter
version: 7.3.14

Sails.js 1.1.0 Security issue: Upgrade lodash to version 4.17.13 or later

I created a new project using Sails.js and when I pushed it to github I am getting a security alert:
Upgrade lodash to version 4.17.13 or later
Problem is I can't seem to upgrade the lodash version. Sails is using "#sailshq/lodash": "^3.10.3" I tried yarn install lodash#4.17.13 but the yarn.lock still have the old version.
Anybody knows how to upgrade the lodash version?
Here is the full alert:
CVE-2019-10744
high severity
Vulnerable versions: < 4.17.13
Patched version: 4.17.13
Affected versions of lodash are vulnerable to Prototype Pollution.
The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.

new Capistrano version 2.6.0 deploy error: `sync' is not implemented by Capistrano::Deploy::SCM::None (rsync with remote cache)

I'm using Capistrano along with the capistrano_rsync_with_remote_cache gem when deploying applications.
The problem occourred after upgrading the deploy server with new software:
capistrano 2.5.10 -> 2.6.0
capistrano_rsync_with_remote_cache 2.3.6 -> 2.4.0
ruby 1.8.6 -> 1.8.7
ruby-gems 1.3.5 -> 1.3.7
the error message:
http://pastebin.com/bD3azxFZ
The top most error:
/var/lib/gems/1.8/gems/capistrano-2.6.0/lib/capistrano/recipes/deploy/scm/base.rb:94:in sync': sync' is not implemented by Capistrano::Deploy::SCM::None (NotImplementedError) from
/var/lib/gems/1.8/gems/capistrano_rsync_with_remote_cache-2.4.0/lib/capistrano/recipes/deploy/strategy/rsync_with_remote_cache.rb:110:in
The line from the file rsync_with_remote_cache.rb:110:
source.sync(revision, local_cache_path)
However this is the same line used in the previous version (2.3.6) of capistrano_rsync_with_remote_cache where the NotImplementedError isn't pressent.
The deploy.rb file used with both versions
http://pastebin.com/EbPkCxyN
what should I change in order to make it deploy again with the newer version?
Sync only works when an SCM is set. You have set :scm, :none in your deploy.rb. Change it accordingly to your SCM. set :scm, :git or the likeā€¦
Just had the same error here and got it fixed and thought more people might run into this - and apparently do.