chore(deps): update prisma dependencies to v4.15.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@prisma/client (source)	4.6.1 -> 4.15.0
prisma (source)	4.6.1 -> 4.15.0

---

Release Notes

prisma/prisma

v4.15.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

For this release, we focused on fixing bugs and making smaller quality-of-life improvements.

Support for custom arguments for prisma db seed

This release adds support for defining and passing arbitrary arguments to prisma db seed. This creates the opportunity for you to define your own arguments in your seed file that you could pass to the prisma db seed command. A few example use-cases include, but are not limited to:

• Seeding different data in different environments
• Partially seeding data in some tables

Here is an example seed.ts file that defines custom arguments for seeding different data in different environments:

// prisma/seed.ts
import { parseArgs } from "node:util";

const options = {
  environment: { type: 'string', },
}

async function main() {
  const { values: { environment } } = parseArgs({ options })
  
  switch (environment) {
    case "development":
      /** do something for development */
      break;
    case "test":
      /** do something  for test  environment */
      break;
    default:
      break;
  }
}

main()

You can then provide the environment argument when executing the seed script as follows:

npx prisma db seed -- --environment development

Let us know what you think, share example usage of this feature, and create a bug report if you run into any issues.

Improved error messages when Query Engine file is not found

This release improves the error messages returned by Prisma Client when the Query Engine file is not found. A few reasons the Query Engine file might be missing from your application bundle include when:

• The downloaded Query Engine doesn’t match the runtime/ target platform your application is running on.
• The Query Engine is not copied to your final application bundle during the build step.

We hope these error messages are helpful while debugging your application.

Prisma VS Code extension improvements

In this release, we made a few improvements to our VS Code extension:

1. Updated the file system watcher that is responsible for restarting the TypeScript server when prisma generate is run to ensure the types are in sync

   Note:

   • This new approach is currently only available on Windows and Linux. We plan on adding support for the new file system watcher on macOS soon.
   • This requires both Prisma CLI & VS code extension version 4.15.0 or higher

2. Added Quick Fixes action for unique identifiers for MongoDB to add the @map("_id") attribute function when it’s missing on an identifier field

   Screen.Recording.2023-05-17.at.19.22.20.mov

3. Support for renaming symbols for composite types and views

   type-symbol-rename.mov

Fixes and improvements

Prisma Client

• Prisma generate - Error: write EPIPE on WSL <-> Windows
• prisma generate is blocked by query-engine-rhel-openssl-1.0.x opening in Notepad on Windows
• Generated client output path hardcoded to build environment
• Issue with Yarn Workspace Monorepo: Query engine binary for current platform could not be found.
• Cloning a project with checked in node_modules (from another platform) leads to platform engine not being present
• SvelteKit, Vite and Prisma "module not defined"
• Schema File Not Found in non monorepo with custom output
• Deploying to Cloudflare Workers | "PrismaClient is unable to be run in the browser"
• Inline/bundle the contents of the prisma schema on generate
• Netlify: Query engine library for current platform "rhel-openssl-1.0.x" could not be found. You incorrectly pinned it to rhel-openssl-1.0.x
• Query Engine Library Not Found
• No client schema when using PrismaClient during cached (standard) Netlify build
• Module "@​prisma/client" has no exported member "PrismaClient"
• EPERM: operation not permitted
• prisma/client crashes when used with older versions of react-refresh
• Unable to run prisma cli in pnpm monorepo from workspace install
• Misleading error message when the query engine is not found
• When setting custom client output directory, generated package.json does not include "sideEffects: false"
• You already added the platform "debian-openssl-1.1.x" to the "generator" block in the "schema.prisma" file as described in https://pris.ly/d/client-generator, but something went wrong.
• Prisma seems to be looking in the wrong location for rhel-openssl-1.0.x
• Can't find prisma engine
• Cannot find name '$PrismaModel' due to feature extendedWhereUnique with preview feature fieldReference
• Netlify build fails with PrismaClientInitializationError
• i'm getting the error while requesting the api
• Query engine library for current platform could not be found.
• Prisma unable to reconnect if initial connection fails
• GraphQL protocol encoder incorrectly turns empty array into empty object.
• GraphQL protocol: Invalid Date values silently turn into nulls
• @​prisma/client/edge + Cloudflare Worker / wrangler = Could not resolve "os"
• Client is bricked from connecting to DB if first attempt fails.
• JSON protocol: incorrect recursive composites detection through multiple nesting levels
• fieldReference is not working with enums

Prisma Migrate

• Pass extra arguments to prisma db seed to the seed command
• Typo in generating migration SQL to add enum.

Language tools (e.g. VS Code)

• MongoDB: Quick fix for missing @map("_id") annotation
• Rename composite types
• Views: Support for rename
• TextDocument deprecation
• Lib name change vsce -> @​vscode/vsce

Credits

Huge thanks to @​RobertCraigie, @​KhooHaoYit, @​art049, @​luxaritas, @​mrazauskas, @​maxmartynov, @​haneenmahd for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, June 1 at 5 pm Berlin | 8 am San Francisco.

v4.14.1

Compare Source

Today, we are issuing the 4.14.1 patch release.

Fix in Prisma Client

• @​prisma/client/edge + Cloudflare Worker / wrangler = Could not resolve "os"

v4.14.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Request for feedback for Preview features

We would appreciate your feedback on a handful of Preview features to help us move them to General Availability soon. The Preview features include:

• PostgreSQL extensions
• Extended where unique
• Field reference support
• Order by Nulls
• Count by filtered relation

You can test them by enabling the Preview feature in your Prisma schema and giving them a try already in your Prisma schema, e.g., PostgreSQL extensions, or regenerating Prisma Client and trying them in your queries.

Highlights

Improved Prisma Client startup performance

For the last couple of months, we've been working hard to improve the performance of Prisma Client. We also published a blog post on how How We Sped Up Serverless Cold Starts with Prisma by 9x, which we recommend you give it a read.

This release continues with the same theme by making the size of the generated Prisma Client smaller. We have roughly halved the size of Prisma Client's dependencies.

More Introspection warnings for unsupported features

In 4.13.0, we introduced the first 6 introspection warnings that surface the existence of these features in your database and link to our documentation on how to manually work around the Prisma Schema with unsupported database features.

In this release, we added 3 more introspection warnings for the following features:

• Check Constraints (MySQL + PostgreSQL)
• Exclusion Constraints
• MongoDB $jsonSchema

On introspecting a database using any of these features, you will get a warning from the Prisma CLI and a comment in your Prisma schema where the feature is being used. The warning will also contain a link to instructions on how to manually use the feature.

Fixes and improvements

Prisma Client

• Generator output client leads to Error: ENOENT: no such file or directory, open '.../node_modules/@​prisma/client/schema.prisma'
• DeprecationWarning: Implicit coercion to integer for exit code is deprecated
• thread 'tokio-runtime-worker' panicked at 'internal error: entered unreachable code: No unsupported field should reach that path', query-engine\connectors\sql-query-connector\src\model_extensions\scalar_field.rs:70:44
• jsonProtocol: in argument of filter types does not accept scalars
• jsonProtocol should report errors as nicely as before
• Generated client with custom path containing string client: ENOENT: no such file or directory, open 'D:\<projectpath>\node_modules\.prisma\client\schema.prisma
• Can't find the schema when the project path contains the same name as the generated client folder

Prisma Migrate

• Build all glibc Linux binaries with CentOS 7
• Remove Please create an issue ... in MigrateEngine.ts
• Do not introspect exclusion constraints as Gist indexes
• Introspection warnings: move rendering from DbPull.ts to the engine
• views: don't create local views folder on introspection if no views are found
• RelationMode autocomplete uses incorrect casing

Language tools (e.g. VS Code)

• Support for VSCode Region Marker Folding

Credits

Huge thanks to @​RobertCraigie, @​KhooHaoYit, @​art049, @​luxaritas, @​mrazauskas for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, May 11 at 5 pm Berlin | 8 am San Francisco.

v4.13.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

Introspection warnings for unsupported features

The Prisma Schema Language (PSL) currently doesn't support all database features and functionality of our target databases. The PSL is an abstraction over SQL and will keep evolving to address gaps in our database feature matrix.

Before this release, prisma db pull did not pick up the unsupported features in a database. It was easy to lose them when running prisma migrate dev based on an existing Prisma schema if not included in a migration file using custom migrations.

To avoid this, we added introspection warnings that surface the existence of these features in your database and link to our documentation on how to manually work around the Prisma Schema with unsupported database features.

In this release, we added introspection warnings for the following features:

• Partitioned tables
• PostgreSQL Row Level Security
• Index sort order, NULLS FIRST / NULLS LAST
• CockroachDB row-level TTL
• Comments
• PostgreSQL deferred constraints

Prisma CLI will output warnings on introspection (prisma db pull) and add comments to your Prisma schema. In the coming releases, we will expand this to many more features labeled with topic: database-functionality on GitHub.

Improved support for Netlify and Vercel build process

Netlify and Vercel cache project dependencies during the build process and reuse that cache until dependencies change. While this helps speed up the build process, any postinstall scripts of these dependencies will not be executed.

Prisma uses a postinstall script in its package to automatically trigger the customized generation of Prisma Client for your Prisma Schema. When a dependency cache is used, that generation process is not triggered, and an outdated Prisma Client may be used in your application.

When you update your Prisma Schema but not your dependencies, Prisma Client will not be generated for the new schema. For example, columns you added recently to one of your models will not be present in the Prisma Client API - causing errors.

This problem can be avoided by:

1. Adding a custom postinstall script in your package.json file
2. Manually adding a prisma generate step to the “Build” scripts of Vercel and Netlify.

We now added detection of this scenario and will prevent a build without an additional prisma generate. This will ensure you're aware of the problem early and get guidance on how to fix this problem. You can read more on how to do this in our docs — Vercel caching troubleshooting, Netlify caching troubleshooting.

Better support for pnpm as a package manager

Before this release, Prisma only used npm scripts which would lead to undesirable behavior for a project using a different package manager such as pnpm and yarn. This release improves the detection of the package managers in your project by using ni. If you're still running into this problem, let us know by creating a GitHub issue.

Segmentation fault and TLS connection error fix

In this release, we've fixed a TLS connection error segmentation fault. This mostly affected users running on Node.js 17 or later with OpenSSL 1.1 when using TLS to connect to their database.

JSON protocol Preview feature feedback

We have fixed multiple bugs for the jsonProtocol Preview feature and are close to making it Generally Available. We are still looking for feedback about its usage to ensure it is ready and works as expected for everyone.

We would appreciate it if you would try it out, help us polish the feature, and move it to General Availability. Testing it requires little effort. You can test it using the following steps:

1. Enabling the jsonProtocol Preview feature in your Prisma schema
2. Re-generating Prisma Client
3. Running your application or tests to make sure everything works

We encourage you to leave your feedback in this GitHub issue or create a bug report if your run into any issues.

Fixes and improvements

Prisma Client

• prisma generate fails when using pnpm workspaces because it tries to install prisma dependencies with npm or yarn
• Netlify deploy does not pick up changes to schema file
• Vercel: Schema only change does not invalidate build cache
• Serverless deployments: Just making a schema level change to a repository does not invalidate node_modules cache that contains generated Client
• pnpm: Can not prisma generate when @prisma/client is not installed in project
• Segmentation fault crash when using prisma client when using PostgreSQL
• Docker with pnpm install hangs on @prisma/client postinstall
• Automatic installation of missing dependencies isn't compatible with pnpm
• Prisma generate throws dependency error karma-chai
• Postinstall script fails with PNPM workspaces due to npm ERR! Cannot read properties of null (reading 'matches')
• Debian 11 Node 19.3.0 segmentation fault
• Prisma client segfault on Ubuntu 22.04
• Segmentation Fault in Postgres
• Using Prisma with pnpm results in inability to call database related commands
• Prisma Connect Causes NodeJS to Close With Exit Code 0
• 99056 segmentation fault (core dumped) node --require esbuild-register prisma/seed.ts
• JSON protocol: sibling composites of the same type are rejected

Prisma Migrate

• prisma db pull adds redundant comments: "This table is a partition table ..."
• Render warning code 30 in cli (PG RLS)

Language tools (e.g. VS Code)

• [object Object] output in logging isn't helpful

Credits

Huge thanks to @​KhooHaoYit, @​rintaun, @​maxmartynov, @​haneenmahd for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, April 20 at 5 pm Berlin | 8 am San Francisco.

v4.12.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

Introspection of Views SQL improvements (Preview)

The views Preview feature significantly improved this release: prisma db pull now reads the SQL query used to define a view and stores it in a .sql file in a views folder next to your Prisma schema.

Note: These .sql files are not yet used for creating or updating views during migrations yet. For now, we are only looking for feedback. Let us know if the introspected SQL files match the views picked up in your database and if the correct files were created in your filesystem.

We encourage you to leave feedback in this GitHub issue.

Improvements to JSON protocol (Early Preview)

In 4.11.0, we announced the jsonProtocol Preview feature which had some rough edges. This release improves the Preview feature by providing polished and helpful error messages from Prisma Client when something goes wrong. Here is an example error message:

We would appreciate it if you would try it out to help us polish the feature and move it to General Availability. Testing it requires little effort. Please also leave any feedback in this issue, or open a new one if you want to report a bug.

Prisma Client startup performance

In this release, we've improved the startup performance of Prisma Client. We're keen on improving the performance of Prisma Client. If you experience any problems with the startup performance, be sure to report them so that we can look into them.

Open Telemetry tracing and logging for Prisma Client for Data Proxy

This release adds support for Open Telemetry tracing (via the tracing Preview feature) and logging to Prisma Client for Data Proxy.

Fixes and improvements

Prisma Migrate

• Certain types of schema changes don't work with CockroachDB v22.2
• Completions: provided by engines break right at the start of a newline
• db pull fail with particular enum default value in column
• Unable to reset CockroachDB for table with foreign key relationship on v22.2.
• Introspection of SQLite views
• Changing the Column Type to Enum on a model throws an error
• Introspection of the view definition statement
• MySQL multi-value index removes the primary key on introspection

Prisma Client

• findUnique used with Promise.all returns null
• Missing PrismaPromise export after update from 4.9.0 to 4.11.0
• jsonProtocol doesn't query enum fields by default
• Prisma 4.11 breaks multilevel relation with compound primary keys (typings)
• 4.11.0: Unique constraint failed on the fields on query that worked in 4.10.1
• jsonProtocol Field/Enum is not included in the result of the findFirst/findMany function
• Too many records are returned in 4.11.0 when using nested include and @​unique field is null
• Objects with computed properties returned from an extended prisma client return true for any property name when calling hasOwn or hasOwnProperty on it

Language tools (e.g. VS Code)

• Completions: suggest type block for MongoDB
• Remove datasource completions

Credits

Huge thanks to @​KhooHaoYit, @​rintaun, @​ivan, @​art049 for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, March 30 at 5 pm Berlin | 8 am San Francisco.

v4.11.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

JSON protocol Early Preview

This release introduces an early Preview feature: JSON protocol.

During performance investigations and optimizations, we noticed that the existing implementation added a CPU and memory overhead that was especially noticeable for larger Prisma schemas. Therefore, we found an alternative way to express our queries without needing that overhead: JSON.

To try out the new protocol, enable the jsonProtocol Preview feature in your Prisma schema:

generator client {
  provider        = "prisma-client-js"  
  previewFeatures = ["jsonProtocol"]
}

Regenerate Prisma Client to use the new JSON protocol.

For environments or situations where it is not viable to enable the Preview feature flag to your Prisma schema file, we also added an environment variable that you can use to force the use of the JSON Protocol Preview feature: PRISMA_ENGINE_PROTOCOL=json.

Note: This is an early Preview feature with a significant limitation: Invalid input to Prisma Client will throw unpolished, internal errors that are less descriptive and user-friendly than our usual ones. We intend to improve these future releases. Using it with Data Proxy and Prisma Data Platform currently also leads to errors.

We expect using jsonProtocol to improve Prisma Client's startup performance significantly. This will likely have a more significant impact on applications with larger Prisma schemas.

We would appreciate your feedback on this feature on the following particularly:

1. Does using this preview feature introduce any regressions or problems in your application?
2. If not, how does it influence the performance of your application? Can you share before and after measurements?

For feedback, please comment on the GitHub feedback issue.

Introspection support for MySQL, SQL Server, and CockroachDB views

You can now run prisma db pull against your database to populate your Prisma schema with your views in MySQL, SQL Server, and CockroachDB.

To learn more, refer to our documentation on views introspection. Try it out and let us know your thoughts in this GitHub issue.

Prisma Client extensions improvements: raw query operations

This release adds support for extending top-level raw query operations.

const prisma = new PrismaClient().$extends({
  query: {
    // relational databases
    $queryRaw({ args, query, operation }) {
      // handle $queryRaw operation
      return query(args)
    },
    $executeRaw({ args, query, operation }) {
      // handle $executeRaw operation
      return query(args)
    },
    $queryRawUnsafe({ args, query, operation }) {
      // handle $queryRawUnsafe operation
      return query(args)
    },
    $executeRawUnsafe({ args, query, operation }) {
      // handle $executeRawUnsafe operation
      return query(args)
    },
    // MongoDB
    $runCommandRaw({ args, query, operation }) {
      // handle $runCommandRaw operation
      return query(args)
    },
  },
})

Webpack plugin for Next.js apps using Prisma in monorepo setups

If you've been using Prisma Client in a Next.js app in a monorepo setup, you might have seen this infamous error message:

Error: ENOENT: no such file or directory, open schema.prisma

We finally pinpointed the problem's source to the Next.js bundling step and opened an issue in the Next.js repository for Vercel to investigate and hopefully fix it.

In the meantime, we've created a workaround via a webpack plugin that makes sure your Prisma schema is copied to the correct location: @prisma/nextjs-monorepo-workaround-plugin.

To use the plugin, first install it:

npm install -D @​prisma/nextjs-monorepo-workaround-plugin

Import the plugin into your next.config.js file and use it in config.plugins:

const { PrismaPlugin } = require('@​prisma/nextjs-monorepo-workaround-plugin')
module.exports = {
  webpack: (config, { isServer }) => {
    if (isServer) {
      config.plugins = [...config.plugins, new PrismaPlugin()]
    }
    return config
  },
}

For further information, refer to our documentation to learn how to use it and open an issue if it doesn't work as expected.

Fixes and improvements

Prisma Client

• Prisma hangs when javascript is minified
• Issue with prisma failing to locate schema file in monorepo
• NextJS try to open "schema.prisma" at wrong path.
• pnpm workspace + nextjs: ENOENT: no such file or directory, open '...\.next\server\pages\api\schema.prisma'
• next.js ENOENT trying to open schema.prisma
• Error with custom output in NPM monorepo: Error: ENOENT: no such file or directory, open 'schema.prisma'
• Error with custom output in Turborepo using Blitz.js: Error: ENOENT: no such file or directory, open '<...>/schema.prisma'
• Upsert fails on Postgres with list column.
• Error received when connecting items in an existing one-to-many relationship on MySQL
• ENOENT with custom output and ESM module in NPM monorepo (including Nextjs): no such file or directory, open /.../schema.prisma...
• Setting ignoreEnvVarErrors: true Node API QE causes datasourceOverrides to be ignored
• PCE: Support query extensions for raw queries

Prisma Migrate

• sslaccept=accept_invalid_certs not working with mysql server 8.0.30
• Error 08S01 (1043) -> Bad Handshake. MySQL Connection with SSL certs
• Introspection of MySQL views
• Introspection of SQL Server views
• Introspection of CockroachDB views
• db pull: add new codes for introspection warnings for views in the CLI
• Figure out where getDMMF is used for validation
• Error when directUrl is prisma:// connection string
• 4.10.0, unexpected: errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.
• Validation output is now always colored, also in CI
• Prisma Client falsely validates directUrl env var value, leading to validation error (Affects PDP/Data Proxy and normal Engine)
• Fix Postgres introspection of partition tables false positives on inherited tables
• Support openSUSE Tumbleweed
• Change validate to return Result<(), JsError> in Wasm module
• (internal): add unit tests for path-specific libssl version parsing

Credits

Huge thanks to @​KhooHaoYit, @​rintaun, @​ivan, @​Mini256, @​Lioness100, @​yukukotani, @​sandrewTx08, @​fubhy, @​zachtil, @​unflxw, @​Mosaab-Emam for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, March 2 at 5 pm Berlin | 8 am San Francisco.

v4.10.1

Compare Source

Today, we are issuing the 4.10.1 patch release.

Fixes in Prisma Client

• Prisma Client falsely validates directUrl env var value, leading to validation error (Affects PDP/Data Proxy and normal Engine)
• 4.10.0, unexpected: errorCode: 'P1012' PrismaClientInitializationError: error: Environment variable not found: DATABASE_URL.

v4.10.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

Improved CLI support for connection poolers

When working with connection poolers such as the Prisma Data Proxy, Accelerate or pgBouncer, it is necessary to use a different URL to connect to the database when using Prisma Client and Prisma Migrate.

We're introducing a new datasource property directUrl to improve this. When the directUrl property is present, the Prisma CLI will use it to connect to the database for tasks such as introspection and migrations.

### .env
### Connection to Prisma Data Proxy. Used by Prisma Client.
DATABASE_URL="prisma://__HOST__/?api_key=__KEY__"

### Connection to the database. Used for migrations and introspection.
DIRECT_URL="postgresql://__USER__:__PASSWORD__@​__HOST__:__PORT__/__DATABASE__"

// ./prisma/schema.prisma
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider  = "postgresql"
  url       = env("DATABASE_URL")
  directUrl = env("DIRECT_URL")
}

To learn more, refer to our documentation.

Introspection support for PostgreSQL views

We introduced initial support for database views in 4.9.0 with the addition of the view keyword. This release introduces introspection support for PostgreSQL views. You can run prisma db pull against your database to populate your Prisma schema with your views.

To learn more, refer to our documentation on views introspection. Try it out and let us know your thoughts in this GitHub issue.

Improved introspection for unsupported database functionality & partitioned tables

Currently, the Prisma Schema Language(PSL) does not cover the full feature sets of different database providers. For the unsupported database functionality, Prisma provides offers escape hatches like raw queries or manual editing of the migration files.

While we work on adding support for missing database functionality, e.g. database views, some of it is not fully-supported and the escape hatches fail. Objects that use unsupported properties might not be caught during introspection and raw queries might not work. Re-introspection may sometimes remove the information from the schema file and the generated migrations may be invalid or re-generate the same SQL repeatedly.

We're therefore fixing the defects and supporting the unsupported database functionalities Prisma currently doesn't support. We created a list of these features in this GitHub issue we would like to improve.

This release improves introspection support for partitioned tables in PostgreSQL and MySQL. Previously, Prisma would pick up the partitions as models and miss the actual main table. Prisma will now pick up the main table as a model, not the partitions.

If you're already using partitioned tables in your database, you can use prisma db pull to update your Prisma schema. If you're already using Prisma and want to partition a table in your database, you can:

1. Create a draft migration using prisma migrate dev --create-only
2. Update the draft migration with the SQL to partition the tables
3. Re-run prisma migrate dev to apply the draft migration to your database

Try it out and let us know what you think. If you run into an issue, feel free to create a bug report.

Smaller engine size used in Prisma CLI

In 4.8.0, we decreased the size of the engines by ~50%, which significantly impacted Prisma Client, especially in serverless environments.

In this release, we've reduced the size of Prisma CLI by removing the Introspection and Formatter engines. The introspection functionality is now served by the Migration Engine. A cross-platform Wasm module has entirely replaced the Formatter Engine. This reduces the overall installation size for Prisma CLI.

Fixes and improvements

Prisma Client

• Precompiled engine files for aarch64-unknown-linux-musl target (Alpine Linux on ARM, e.g. M1)
• Specify the generator to use for sharing schema files in different environments
• Implement getDmmf as Wasm module that could be used in Prisma CLI
• Client in interactive transaction is not extended
• Deeply nested objects aren't typed when clientExtensions is enabled
• Typescript issue on nested queries with clientExtensions feature

Prisma

• Introspection can't get composite primary key for partitioned table
• db pull adds redundant comment about ignored table
• Remove prisma-fmt formatter binary
• Diagnostics currently need to be manually written for Code Action tests
• OpenSSL on Node Alpine still not working after Prisma 4.8.0 on an ARM machine
• Improved error messages on system library detection
• Remove introspection-engine binary from CLI
• [Stopgap] Introspect partitioned tables better: Only introspect main table in a valid way, ignore partitions
• Regression: get-platform error for non-amd64 Alpine introduced in prisma@4.9.0 prevents using custom Prisma engines
• Introspection of PostgreSQL views
• internal: use original distro and distro family in warning messages
• Failed to detect linux distro + Error: Unknown binaryTarget debian-openssl-0.0.x and no custom engine files were provided after upgrading from 4.8.1 to 4.9.0

Language tools (e.g. VS Code)

• Add VS Code quick fix / code action to phase out referentialIntegrity in favor of relationMode
• Auto completion of directUrl

Credits

Huge thanks to @​rintaun, @​ivan, @​Mini256, @​yukukotani, @​sandrewTx08 for helping!

📺 Join us for another "What's new in Prisma" live stream

Learn about the latest release and other news from the Prisma community by joining us for another "What's new in Prisma" live stream.

The stream takes place on YouTube on Thursday, February 9 at 5 pm Berlin | 8 am San Francisco.

v4.9.0

Compare Source

🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

Highlights

Initial support for database views (Preview)

This release introduces a new keyword, view, behind the views Preview feature flag. You can manually add a view to your Prisma schema, which is ignored when running migrations. This is a small step forward but should already be helpful to many of you depending on workarounds and shell scripts to work with views and Migrate.

Here is an example usage of views:

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["views"]
}

view UserInfo {
  id    Int    @​id
  // from the User model
  email String
  name  String
  // from the Profile model
  bio   String
}

model User {
  id      Int      @​id @​default(autoincrement())
  email   String   @​unique
  name    String?
  profile Profile?
}

model Profile {
  id     Int    @​id @​default(autoincrement())
  bio    String
  user   User   @​relation(fields: [userId], references: [id])
  userId Int    @​unique
}

To learn more, head to our documentation. Try it out and let us know your thoughts on this GitHub issue.

Multi-schema support for SQL Server (Preview)

We're thrilled to share that this release adds Preview support for multi-schema for SQL Server.

This release adds support for:

• Introspecting databases that organize objects in multiple database schemas
• Managing multi-schema database setups directly from Prisma schema
• Generating migrations that are database schema-aware with Prisma Migrate
• Querying across multiple database schemas with Prisma Client

If you already have a SQL Server database using multiple schemas, you can quickly get up and running and set up multiple schemas by:

• Enabling the Preview feature in the Prisma schema
• Defining the schemas in the schemas property in the datasource block
• Introspecting your database using prisma db pull

You can further evolve your database schema using the multi-schema Preview feature by using prisma migrate dev.

For further details, refer to our documentation and let us know what you think in this GitHub issue.

Prisma Client Extensions improvements

In this release, we've made a number of improvements to the Prisma Client Extensions Preview feature:

1. Retrieving the current model name at runtime
   You can now get the name of the current model at runtime using Prisma.getExtensionContext(this).name. You might use this to write out the model name to a log, to send the name to another service, or to branch your code based on the model. You can learn more about this in our docs.

2. Improved type safety when defining custom model methods
   Prisma Client now provides a set of type utilities that tap into input and output types. They are fully dynamic, which means they adapt to any given model and schema. You can use them to improve your custom model methods' auto-completion. This is especially useful in shared extensions. Learn more about this in our docs.

Let us know what you think in this GitHub issue and in case you run into any issues, please create a bug report.

Introspection and Migration engine improvements

In this release, we moved the Introspection Engine (responsible for prisma db pull) which the Migration Engine will now serve. Previously, the Introspection Engine was stand-alone.

Let us know what you think in this GitHub issue and in case you run into any issues, please create a bug report.

MongoDB WriteConflict bug fix

This version also comes with a notable bug fix: In our MongoDB provider, any queries that are returned with a WriteConflict error Prisma now will retry the query, similar to how other MongoDB drivers and clients do.

Prisma plugin for JetBrains IDEs

If you are using a JetBrains IDE the team over at JetBrains recently released an official Prisma plugin in their Plugin Marketplace.

Thank you, @​JetBrains, for working on this! Next to our VS Code extension for Prisma and our general language server, which works in many editors, most relevant editors should now be covered.

Accelerate (Early Access)

We’re thrilled to announce Early Access to Accelerate.

Accelerate is a global database cache. It is available in 280 locations and has built-in connection pooling for serverless apps. You can make your queries up to 1000 times faster on any Prisma-supported database, reducing your query response times.

Join the waiting list for Accelerate here.

Fixes and improvements

Prisma

• Feature Request: Jetbrains (IntelliJ IDEA, Webstorm) Plugin
• Misleading 'We need to reset the PostgreSQL database' when using PostgreSQL schemas
• Solve "P1012 Introspection failed" errors on Windows CI
• support NanoID
• Create CI worker without a proper openssl or libc installation to improve snapshot testing suite
• db pull --url with an invalid url produces a misleading error message
• (re)-Introspection errors have a misleading error message
• multi-schema + introspection: rename models and enums to avoid name collisions
• multiSchema + introspection: add --schemas param to the db pull command
• Cross schema reference with foreign key not working in 4.7.0+
• Handle missing schemas property different when cross schema references are detected (when multiSchema preview feature is enabled)
• db pull with multiSchema enabled and schemas defined, outputs public in CLI message anyway
• Remove DML dependency from MongoDB introspection
• I want short unique id. UUID, CUID are too long
• Completions: for schemas property in datasource
• Completions @@​schema attribute
• OS Support: improve SSL detection on debian distros
• multiSchema: add schemas property to getConfig output
• multiSchema: migrate reset with sqlserver does not delete second schema
• Prisma 4.9.x (dev version) broke openssl detection for Linux distros besides Alpine and Debian-based distros, like RHEL
• [Wrong db pull warning with multiSchema preview feature, it says that These enums were enriched with @@​map` inform

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖success

Show Plan

terraform
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/CrimLog/dev/runs/run-ctjzx7Syh1b51nh4

Waiting for the plan to start...

Terraform v1.4.5
on linux_amd64
Initializing plugins and modules...
aws_ecs_cluster.cluster: Refreshing state... [id=arn:aws:ecs:us-east-1:479401498383:cluster/graphql-api-dev]
data.aws_acm_certificate.cert: Refreshing...
aws_cloudwatch_log_group.log_group: Refreshing state... [id=/ecs/graphql-api-dev]
aws_vpc.vpc: Refreshing state... [id=vpc-071c87c56b8eca1be]
aws_default_vpc.vpc: Refreshing state... [id=vpc-04a957e07df5e4290]
aws_iam_role.ecs_task_execution_role: Refreshing state... [id=graphql-api-dev-execution-role]
aws_iam_policy.fargate_policy: Refreshing state... [id=arn:aws:iam::479401498383:policy/graphql-api-dev-fargate-policy]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment1: Refreshing state... [id=graphql-api-dev-execution-role-20230419232626349200000002]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment2: Refreshing state... [id=graphql-api-dev-execution-role-20230419232626332000000001]
aws_ecs_task_definition.definition: Refreshing state... [id=graphql-api-dev-task]
data.aws_acm_certificate.cert: Refresh complete after 0s [id=arn:aws:acm:us-east-1:479401498383:certificate/71f48b3d-ceca-4b5f-bcb9-4b8055d23758]
aws_security_group.graphql_api: Refreshing state... [id=sg-091e4a09d3a5eaeec]
aws_subnet.subnet["us-east-1d"]: Refreshing state... [id=subnet-0cbd4d58eb64dbcb2]
aws_subnet.subnet["us-east-1b"]: Refreshing state... [id=subnet-070be33c50d6962da]
aws_default_security_group.default: Refreshing state... [id=sg-0fa73ffe645781826]
aws_security_group.web_everyone2: Refreshing state... [id=sg-09d11e5205916ea28]
aws_lb_target_group.target_group: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:479401498383:targetgroup/graphql-api-dev/5347bfb4422bb66c]
aws_vpc_peering_connection.peering_connection: Refreshing state... [id=pcx-093ce57d2df3df5dd]
aws_internet_gateway.gw: Refreshing state... [id=igw-0ce407fc154b8cb2c]
aws_route.vpc_peering_route: Refreshing state... [id=r-rtb-023d93e86e836cb4b2811395018]
aws_default_route_table.default: Refreshing state... [id=rtb-0a657c4a4dd0540c7]
aws_lb.alb: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:479401498383:loadbalancer/app/graphql-api-dev-alb/b6f57001c89afb4a]
aws_ecs_service.service: Refreshing state... [id=arn:aws:ecs:us-east-1:479401498383:service/graphql-api-dev/graphql-api-dev-svc]
aws_lb_listener.listener: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:479401498383:listener/app/graphql-api-dev-alb/b6f57001c89afb4a/9d6cbfda849869bc]
aws_ecs_task_definition.definition: Drift detected (update)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # aws_ecs_service.service will be updated in-place
  ~ resource "aws_ecs_service" "service" {
        id                                 = "arn:aws:ecs:us-east-1:479401498383:service/graphql-api-dev/graphql-api-dev-svc"
        name                               = "graphql-api-dev-svc"
        tags                               = {}
      ~ task_definition                    = "arn:aws:ecs:us-east-1:479401498383:task-definition/graphql-api-dev-task:2" -> (known after apply)
        # (15 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

  # aws_ecs_task_definition.definition must be replaced
-/+ resource "aws_ecs_task_definition" "definition" {
      ~ arn                      = "arn:aws:ecs:us-east-1:479401498383:task-definition/graphql-api-dev-task:2" -> (known after apply)
      ~ arn_without_revision     = "arn:aws:ecs:us-east-1:479401498383:task-definition/graphql-api-dev-task" -> (known after apply)
      ~ container_definitions    = jsonencode(
          ~ [
              ~ {
                  ~ image            = "479401498383.dkr.ecr.us-east-1.amazonaws.com/graphql-api:7666a1ec2efb24db3a2e09a983dd5ae6ad121646" -> "479401498383.dkr.ecr.us-east-1.amazonaws.com/graphql-api:a5ba767b3fc25d05d1e5e099865cd07fc94b3972"
                    name             = "graphql-api-dev-container"
                    # (8 unchanged attributes hidden)
                },
            ] # forces replacement
        )
      ~ id                       = "graphql-api-dev-task" -> (known after apply)
      ~ revision                 = 2 -> (known after apply)
      - tags                     = {} -> null
      ~ tags_all                 = {} -> (known after apply)
        # (7 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 1 to add, 1 to change, 1 to destroy.

Pushed by: @renovate[bot], Action: pull_request, Environment: dev

[github-actions]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖success

Show Plan

terraform
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/CrimLog/dev/runs/run-GfN5UpqTYFHhunqS

Waiting for the plan to start...

Terraform v1.4.5
on linux_amd64
Initializing plugins and modules...
aws_default_vpc.vpc: Refreshing state... [id=vpc-05493280cd154e867]
aws_cloudwatch_log_group.log_group: Refreshing state... [id=/ecs/graphql-api-test]
aws_iam_policy.fargate_policy: Refreshing state... [id=arn:aws:iam::043894507808:policy/graphql-api-test-fargate-policy]
aws_iam_role.ecs_task_execution_role: Refreshing state... [id=graphql-api-test-execution-role]
data.aws_acm_certificate.cert: Refreshing...
aws_vpc.vpc: Refreshing state... [id=vpc-0ee6fa0c508a5ca80]
aws_ecs_cluster.cluster: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:cluster/graphql-api-test]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment2: Refreshing state... [id=graphql-api-test-execution-role-20230420170658951000000001]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment1: Refreshing state... [id=graphql-api-test-execution-role-20230420170658980700000002]
aws_ecs_task_definition.definition: Refreshing state... [id=graphql-api-test-task]
data.aws_acm_certificate.cert: Refresh complete after 1s [id=arn:aws:acm:us-east-1:043894507808:certificate/bf306bea-c739-451e-bc54-bfd24909b37c]
aws_internet_gateway.gw: Refreshing state... [id=igw-03b3f72ff588c7b80]
aws_ecs_task_definition.definition: Drift detected (update)
aws_iam_policy.fargate_policy: Drift detected (update)
aws_cloudwatch_log_group.log_group: Drift detected (update)
aws_ecs_cluster.cluster: Drift detected (update)
aws_iam_role.ecs_task_execution_role: Drift detected (update)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # aws_cloudwatch_log_group.log_group must be replaced
-/+ resource "aws_cloudwatch_log_group" "log_group" {
      ~ arn               = "arn:aws:logs:us-east-1:043894507808:log-group:/ecs/graphql-api-test" -> (known after apply)
      ~ id                = "/ecs/graphql-api-test" -> (known after apply)
      ~ name              = "/ecs/graphql-api-test" -> "/ecs/graphql-api-dev" # forces replacement
      + name_prefix       = (known after apply)
      - tags              = {} -> null
      ~ tags_all          = {} -> (known after apply)
        # (2 unchanged attributes hidden)
    }

  # aws_default_route_table.default will be created
  + resource "aws_default_route_table" "default" {
      + arn                    = (known after apply)
      + default_route_table_id = "rtb-02f716fd76bdb9cf4"
      + id                     = (known after apply)
      + owner_id               = (known after apply)
      + route                  = [
          + {
              + cidr_block                 = "0.0.0.0/0"
              + core_network_arn           = ""
              + destination_prefix_list_id = ""
              + egress_only_gateway_id     = ""
              + gateway_id                 = "igw-03b3f72ff588c7b80"
              + instance_id                = ""
              + ipv6_cidr_block            = ""
              + nat_gateway_id             = ""
              + network_interface_id       = ""
              + transit_gateway_id         = ""
              + vpc_endpoint_id            = ""
              + vpc_peering_connection_id  = ""
            },
          + {
              + cidr_block                 = "172.31.0.0/16"
              + core_network_arn           = ""
              + destination_prefix_list_id = ""
              + egress_only_gateway_id     = ""
              + gateway_id                 = ""
              + instance_id                = ""
              + ipv6_cidr_block            = ""
              + nat_gateway_id             = ""
              + network_interface_id       = ""
              + transit_gateway_id         = ""
              + vpc_endpoint_id            = ""
              + vpc_peering_connection_id  = (known after apply)
            },
        ]
      + tags_all               = (known after apply)
      + vpc_id                 = (known after apply)
    }

  # aws_default_security_group.default will be created
  + resource "aws_default_security_group" "default" {
      + arn                    = (known after apply)
      + description            = (known after apply)
      + egress                 = [
          + {
              + cidr_blocks      = [
                  + "0.0.0.0/0",
                ]
              + description      = ""
              + from_port        = 0
              + ipv6_cidr_blocks = []
              + prefix_list_ids  = []
              + protocol         = "-1"
              + security_groups  = []
              + self             = false
              + to_port          = 0
            },
        ]
      + id                     = (known after apply)
      + ingress                = [
          + {
              + cidr_blocks      = [
                  + "172.33.0.0/16",
                ]
              + description      = "Default graphql-api-dev VPC"
              + from_port        = 5432
              + ipv6_cidr_blocks = []
              + prefix_list_ids  = []
              + protocol         = "tcp"
              + security_groups  = []
              + self             = false
              + to_port          = 5432
            },
        ]
      + name                   = (known after apply)
      + name_prefix            = (known after apply)
      + owner_id               = (known after apply)
      + revoke_rules_on_delete = false
      + tags                   = {
          + "Name" = "RDS-Postgres graphql-api-dev"
        }
      + tags_all               = {
          + "Name" = "RDS-Postgres graphql-api-dev"
        }
      + vpc_id                 = "vpc-0ee6fa0c508a5ca80"
    }

  # aws_ecs_cluster.cluster must be replaced
-/+ resource "aws_ecs_cluster" "cluster" {
      ~ arn                = "arn:aws:ecs:us-east-1:043894507808:cluster/graphql-api-test" -> (known after apply)
      ~ capacity_providers = [] -> (known after apply)
      ~ id                 = "arn:aws:ecs:us-east-1:043894507808:cluster/graphql-api-test" -> (known after apply)
      ~ name               = "graphql-api-test" -> "graphql-api-dev" # forces replacement
      - tags               = {} -> null
      ~ tags_all           = {} -> (known after apply)

        # (1 unchanged block hidden)
    }

  # aws_ecs_service.service will be created
  + resource "aws_ecs_service" "service" {
      + cluster                            = (known after apply)
      + deployment_maximum_percent         = 200
      + deployment_minimum_healthy_percent = 100
      + desired_count                      = 1
      + enable_ecs_managed_tags            = true
      + enable_execute_command             = false
      + health_check_grace_period_seconds  = 0
      + iam_role                           = (known after apply)
      + id                                 = (known after apply)
      + launch_type                        = "FARGATE"
      + name                               = "graphql-api-dev-svc"
      + platform_version                   = "LATEST"
      + propagate_tags                     = "NONE"
      + scheduling_strategy                = "REPLICA"
      + tags_all                           = (known after apply)
      + task_definition                    = (known after apply)
      + triggers                           = (known after apply)
      + wait_for_steady_state              = false

      + deployment_circuit_breaker {
          + enable   = false
          + rollback = false
        }

      + deployment_controller {
          + type = "ECS"
        }

      + load_balancer {
          + container_name   = "graphql-api-dev-container"
          + container_port   = 80
          + target_group_arn = (known after apply)
        }

      + network_configuration {
          + assign_public_ip = true
          + security_groups  = (known after apply)
          + subnets          = (known after apply)
        }
    }

  # aws_ecs_task_definition.definition must be replaced
-/+ resource "aws_ecs_task_definition" "definition" {
      ~ arn                      = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-test-task:1" -> (known after apply)
      ~ arn_without_revision     = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-test-task" -> (known after apply)
      ~ container_definitions    = jsonencode(
          ~ [
              ~ {
                  ~ environment      = [
                      ~ {
                            name  = "NODE_ENV"
                          ~ value = "test" -> "dev"
                        },
                        {
                            name  = "PORT"
                            value = "80"
                        },
                    ]
                  ~ image            = "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:latest" -> "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:1ab5516c67abf9848f400d48b5be9ee58d002a33"
                  ~ logConfiguration = {
                      ~ options   = {
                          ~ awslogs-group         = "/ecs/graphql-api-test" -> "/ecs/graphql-api-dev"
                            # (2 unchanged attributes hidden)
                        }
                        # (1 unchanged attribute hidden)
                    }
                  ~ name             = "graphql-api-test-container" -> "graphql-api-dev-container"
                  ~ secrets          = [
                      ~ {
                            name      = "JWT_SECRET"
                          ~ valueFrom = "arn:aws:secretsmanager:us-east-1:479401498383:secret:graphql-api-secrets-46UvoX:JWT_SECRET::" -> "arn:aws:secretsmanager:us-east-1:043894507808:secret:graphql-api-secrets-ajTuEN:JWT_SECRET::"
                        },
                      ~ {
                            name      = "DATABASE_URL"
                          ~ valueFrom = "arn:aws:secretsmanager:us-east-1:479401498383:secret:graphql-api-secrets-46UvoX:DATABASE_URL::" -> "arn:aws:secretsmanager:us-east-1:043894507808:secret:graphql-api-secrets-ajTuEN:DATABASE_URL::"
                        },
                      ~ {
                            name      = "ALCHEMY_API_KEY"
                          ~ valueFrom = "arn:aws:secretsmanager:us-east-1:479401498383:secret:graphql-api-secrets-46UvoX:ALCHEMY_API_KEY::" -> "arn:aws:secretsmanager:us-east-1:043894507808:secret:graphql-api-secrets-ajTuEN:ALCHEMY_API_KEY::"
                        },
                      ~ {
                            name      = "MATIC_PRIVATE_KEY"
                          ~ valueFrom = "arn:aws:secretsmanager:us-east-1:479401498383:secret:graphql-api-secrets-46UvoX:MATIC_PRIVATE_KEY::" -> "arn:aws:secretsmanager:us-east-1:043894507808:secret:graphql-api-secrets-ajTuEN:MATIC_PRIVATE_KEY::"
                        },
                    ]
                    # (5 unchanged attributes hidden)
                },
            ] # forces replacement
        )
      ~ execution_role_arn       = "arn:aws:iam::043894507808:role/graphql-api-test-execution-role" # forces replacement -> (known after apply)
      ~ family                   = "graphql-api-test-task" -> "graphql-api-dev-task" # forces replacement
      ~ id                       = "graphql-api-test-task" -> (known after apply)
      ~ revision                 = 1 -> (known after apply)
      - tags                     = {} -> null
      ~ tags_all                 = {} -> (known after apply)
        # (5 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

  # aws_iam_policy.fargate_policy must be replaced
-/+ resource "aws_iam_policy" "fargate_policy" {
      ~ arn         = "arn:aws:iam::043894507808:policy/graphql-api-test-fargate-policy" -> (known after apply)
      ~ id          = "arn:aws:iam::043894507808:policy/graphql-api-test-fargate-policy" -> (known after apply)
      ~ name        = "graphql-api-test-fargate-policy" -> "graphql-api-dev-fargate-policy" # forces replacement
      + name_prefix = (known after apply)
      ~ policy_id   = "ANPAQUOCRBEQFIOU4CLJ7" -> (known after apply)
      - tags        = {} -> null
      ~ tags_all    = {} -> (known after apply)
        # (3 unchanged attributes hidden)
    }

  # aws_iam_role.ecs_task_execution_role must be replaced
-/+ resource "aws_iam_role" "ecs_task_execution_role" {
      ~ arn                   = "arn:aws:iam::043894507808:role/graphql-api-test-execution-role" -> (known after apply)
      ~ create_date           = "2023-04-20T17:06:58Z" -> (known after apply)
      ~ id                    = "graphql-api-test-execution-role" -> (known after apply)
      ~ managed_policy_arns   = [
          - "arn:aws:iam::043894507808:policy/graphql-api-test-fargate-policy",
          - "arn:aws:iam::aws:policy/service-role/AmazonECSTaskExecutionRolePolicy",
        ] -> (known after apply)
      ~ name                  = "graphql-api-test-execution-role" -> "graphql-api-dev-execution-role" # forces replacement
      + name_prefix           = (known after apply)
      - tags                  = {} -> null
      ~ tags_all              = {} -> (known after apply)
      ~ unique_id             = "AROAQUOCRBEQGPSU7GEUG" -> (known after apply)
        # (4 unchanged attributes hidden)
    }

  # aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment1 must be replaced
-/+ resource "aws_iam_role_policy_attachment" "ecs-task-execution-role-policy-attachment1" {
      ~ id         = "graphql-api-test-execution-role-20230420170658980700000002" -> (known after apply)
      ~ role       = "graphql-api-test-execution-role" -> "graphql-api-dev-execution-role" # forces replacement
        # (1 unchanged attribute hidden)
    }

  # aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment2 must be replaced
-/+ resource "aws_iam_role_policy_attachment" "ecs-task-execution-role-policy-attachment2" {
      ~ id         = "graphql-api-test-execution-role-20230420170658951000000001" -> (known after apply)
      ~ policy_arn = "arn:aws:iam::043894507808:policy/graphql-api-test-fargate-policy" # forces replacement -> (known after apply)
      ~ role       = "graphql-api-test-execution-role" -> "graphql-api-dev-execution-role" # forces replacement
    }

  # aws_lb.alb will be created
  + resource "aws_lb" "alb" {
      + arn                                         = (known after apply)
      + arn_suffix                                  = (known after apply)
      + desync_mitigation_mode                      = "defensive"
      + dns_name                                    = (known after apply)
      + drop_invalid_header_fields                  = false
      + enable_deletion_protection                  = false
      + enable_http2                                = true
      + enable_tls_version_and_cipher_suite_headers = false
      + enable_waf_fail_open                        = false
      + enable_xff_client_port                      = false
      + id                                          = (known after apply)
      + idle_timeout                                = 60
      + internal                                    = false
      + ip_address_type                             = "ipv4"
      + load_balancer_type                          = "application"
      + name                                        = "graphql-api-dev-alb"
      + preserve_host_header                        = false
      + security_groups                             = (known after apply)
      + subnets                                     = (known after apply)
      + tags_all                                    = (known after apply)
      + vpc_id                                      = (known after apply)
      + xff_header_processing_mode                  = "append"
      + zone_id                                     = (known after apply)
    }

  # aws_lb_listener.listener will be created
  + resource "aws_lb_listener" "listener" {
      + arn               = (known after apply)
      + certificate_arn   = "arn:aws:acm:us-east-1:043894507808:certificate/bf306bea-c739-451e-bc54-bfd24909b37c"
      + id                = (known after apply)
      + load_balancer_arn = (known after apply)
      + port              = 443
      + protocol          = "HTTPS"
      + ssl_policy        = "ELBSecurityPolicy-2016-08"
      + tags_all          = (known after apply)

      + default_action {
          + order            = 1
          + target_group_arn = (known after apply)
          + type             = "forward"
        }
    }

  # aws_lb_target_group.target_group will be created
  + resource "aws_lb_target_group" "target_group" {
      + arn                                = (known after apply)
      + arn_suffix                         = (known after apply)
      + connection_termination             = false
      + deregistration_delay               = "300"
      + id                                 = (known after apply)
      + ip_address_type                    = "ipv4"
      + lambda_multi_value_headers_enabled = false
      + load_balancing_algorithm_type      = "round_robin"
      + load_balancing_cross_zone_enabled  = (known after apply)
      + name                               = "graphql-api-dev"
      + port                               = 80
      + preserve_client_ip                 = (known after apply)
      + protocol                           = "HTTP"
      + protocol_version                   = "HTTP1"
      + proxy_protocol_v2                  = false
      + slow_start                         = 0
      + tags_all                           = (known after apply)
      + target_type                        = "ip"
      + vpc_id                             = "vpc-0ee6fa0c508a5ca80"

      + health_check {
          + enabled             = true
          + healthy_threshold   = 3
          + interval            = 60
          + matcher             = "200"
          + path                = "/health"
          + port                = "traffic-port"
          + protocol            = "HTTP"
          + timeout             = 5
          + unhealthy_threshold = 2
        }

      + stickiness {
          + cookie_duration = 86400
          + enabled         = false
          + type            = "lb_cookie"
        }
    }

  # aws_route.vpc_peering_route will be created
  + resource "aws_route" "vpc_peering_route" {
      + destination_cidr_block    = "172.33.0.0/16"
      + id                        = (known after apply)
      + instance_id               = (known after apply)
      + instance_owner_id         = (known after apply)
      + network_interface_id      = (known after apply)
      + origin                    = (known after apply)
      + route_table_id            = "rtb-028683c282ba5ed8c"
      + state                     = (known after apply)
      + vpc_peering_connection_id = (known after apply)
    }

  # aws_security_group.graphql_api will be created
  + resource "aws_security_group" "graphql_api" {
      + arn                    = (known after apply)
      + description            = "Managed by Terraform"
      + egress                 = [
          + {
              + cidr_blocks      = [
                  + "0.0.0.0/0",
                ]
              + description      = ""
              + from_port        = 0
              + ipv6_cidr_blocks = []
              + prefix_list_ids  = []
              + protocol         = "-1"
              + security_groups  = []
              + self             = false
              + to_port          = 0
            },
        ]
      + id                     = (known after apply)
      + ingress                = [
          + {
              + cidr_blocks      = [
                  + "0.0.0.0/0",
                ]
              + description      = ""
              + from_port        = 80
              + ipv6_cidr_blocks = []
              + prefix_list_ids  = []
              + protocol         = "tcp"
              + security_groups  = []
              + self             = false
              + to_port          = 80
            },
        ]
      + name                   = "graphql-api-dev"
      + name_prefix            = (known after apply)
      + owner_id               = (known after apply)
      + revoke_rules_on_delete = false
      + tags_all               = (known after apply)
      + vpc_id                 = "vpc-0ee6fa0c508a5ca80"
    }

  # aws_security_group.web_everyone2 will be created
  + resource "aws_security_group" "web_everyone2" {
      + arn                    = (known after apply)
      + description            = "Allow web traffic from everyone"
      + egress                 = [
          + {
              + cidr_blocks      = [
                  + "0.0.0.0/0",
                ]
              + description      = ""
              + from_port        = 0
              + ipv6_cidr_blocks = []
              + prefix_list_ids  = []
              + protocol         = "-1"
              + security_groups  = []
              + self             = false
              + to_port          = 0
            },
        ]
      + id                     = (known after apply)
      + ingress                = [
          + {
              + cidr_blocks      = [
                  + "0.0.0.0/0",
                ]
              + description      = ""
              + from_port        = 443
              + ipv6_cidr_blocks = [
                  + "::/0",
                ]
              + prefix_list_ids  = []
              + protocol         = "tcp"
              + security_groups  = []
              + self             = false
              + to_port          = 443
            },
          + {
              + cidr_blocks      = [
                  + "0.0.0.0/0",
                ]
              + description      = ""
              + from_port        = 80
              + ipv6_cidr_blocks = [
                  + "::/0",
                ]
              + prefix_list_ids  = []
              + protocol         = "tcp"
              + security_groups  = []
              + self             = false
              + to_port          = 80
            },
        ]
      + name                   = "web-everyone2"
      + name_prefix            = (known after apply)
      + owner_id               = (known after apply)
      + revoke_rules_on_delete = false
      + tags                   = {
          + "Name" = "web-everyone2"
        }
      + tags_all               = {
          + "Name" = "web-everyone2"
        }
      + vpc_id                 = "vpc-0ee6fa0c508a5ca80"
    }

  # aws_subnet.subnet["us-east-1b"] will be created
  + resource "aws_subnet" "subnet" {
      + arn                                            = (known after apply)
      + assign_ipv6_address_on_creation                = false
      + availability_zone                              = "us-east-1b"
      + availability_zone_id                           = (known after apply)
      + cidr_block                                     = "172.33.0.0/18"
      + enable_dns64                                   = false
      + enable_resource_name_dns_a_record_on_launch    = false
      + enable_resource_name_dns_aaaa_record_on_launch = false
      + id                                             = (known after apply)
      + ipv6_cidr_block_association_id                 = (known after apply)
      + ipv6_native                                    = false
      + map_public_ip_on_launch                        = true
      + owner_id                                       = (known after apply)
      + private_dns_hostname_type_on_launch            = "ip-name"
      + tags_all                                       = (known after apply)
      + vpc_id                                         = "vpc-0ee6fa0c508a5ca80"
    }

  # aws_subnet.subnet["us-east-1d"] will be created
  + resource "aws_subnet" "subnet" {
      + arn                                            = (known after apply)
      + assign_ipv6_address_on_creation                = false
      + availability_zone                              = "us-east-1d"
      + availability_zone_id                           = (known after apply)
      + cidr_block                                     = "172.33.64.0/18"
      + enable_dns64                                   = false
      + enable_resource_name_dns_a_record_on_launch    = false
      + enable_resource_name_dns_aaaa_record_on_launch = false
      + id                                             = (known after apply)
      + ipv6_cidr_block_association_id                 = (known after apply)
      + ipv6_native                                    = false
      + map_public_ip_on_launch                        = true
      + owner_id                                       = (known after apply)
      + private_dns_hostname_type_on_launch            = "ip-name"
      + tags_all                                       = (known after apply)
      + vpc_id                                         = "vpc-0ee6fa0c508a5ca80"
    }

  # aws_vpc_peering_connection.peering_connection will be created
  + resource "aws_vpc_peering_connection" "peering_connection" {
      + accept_status = (known after apply)
      + auto_accept   = true
      + id            = (known after apply)
      + peer_owner_id = (known after apply)
      + peer_region   = (known after apply)
      + peer_vpc_id   = "vpc-05493280cd154e867"
      + tags          = {
          + "Name" = "VPC Peering between main vpc and graphql-api-dev"
        }
      + tags_all      = {
          + "Name" = "VPC Peering between main vpc and graphql-api-dev"
        }
      + vpc_id        = "vpc-0ee6fa0c508a5ca80"

      + accepter {
          + allow_classic_link_to_remote_vpc = false
          + allow_remote_vpc_dns_resolution  = true
          + allow_vpc_to_remote_classic_link = false
        }

      + requester {
          + allow_classic_link_to_remote_vpc = false
          + allow_remote_vpc_dns_resolution  = true
          + allow_vpc_to_remote_classic_link = false
        }
    }

Plan: 19 to add, 0 to change, 7 to destroy.

Pushed by: @renovate[bot], Action: pull_request, Environment: dev

[github-actions]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖success

Show Plan

terraform
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/CrimLog/dev/runs/run-ajWCs9DvT5L7PQrn

Waiting for the plan to start...

Terraform v1.4.5
on linux_amd64
Initializing plugins and modules...
data.aws_acm_certificate.cert: Refreshing...
aws_default_vpc.vpc: Refreshing state... [id=vpc-0d6048d87526ca2aa]
aws_iam_policy.fargate_policy: Refreshing state... [id=arn:aws:iam::043894507808:policy/graphql-api-dev-fargate-policy]
aws_iam_role.ecs_task_execution_role: Refreshing state... [id=graphql-api-dev-execution-role]
aws_cloudwatch_log_group.log_group: Refreshing state... [id=/ecs/graphql-api-dev]
aws_vpc.vpc: Refreshing state... [id=vpc-03a107da2c461f1ed]
aws_ecs_cluster.cluster: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:cluster/graphql-api-dev]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment1: Refreshing state... [id=graphql-api-dev-execution-role-20230423033833450400000002]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment2: Refreshing state... [id=graphql-api-dev-execution-role-20230423033833430200000001]
aws_ecs_task_definition.definition: Refreshing state... [id=graphql-api-dev-task]
data.aws_acm_certificate.cert: Refresh complete after 1s [id=arn:aws:acm:us-east-1:043894507808:certificate/bf306bea-c739-451e-bc54-bfd24909b37c]
aws_subnet.subnet["us-east-1d"]: Refreshing state... [id=subnet-0484d9eacb0f6cc72]
aws_internet_gateway.gw: Refreshing state... [id=igw-0d8b8f92744a512ba]
aws_subnet.subnet["us-east-1b"]: Refreshing state... [id=subnet-08aa670a6d49611ee]
aws_vpc_peering_connection.peering_connection: Refreshing state... [id=pcx-01464ec77db02b015]
aws_security_group.graphql_api: Refreshing state... [id=sg-094dfee2fdebea749]
aws_security_group.web_everyone2: Refreshing state... [id=sg-0c52ea438fe27e25e]
aws_default_security_group.default: Refreshing state... [id=sg-004261418534134d1]
aws_lb_target_group.target_group: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:targetgroup/graphql-api-dev/8bd964a2078b31fb]
aws_route.vpc_peering_route: Refreshing state... [id=r-rtb-09b02ae3a536a3f7a2811395018]
aws_default_route_table.default: Refreshing state... [id=rtb-010126cd65b1352bc]
aws_lb.alb: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:loadbalancer/app/graphql-api-dev-alb/83649cc106b45569]
aws_ecs_service.service: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc]
aws_lb_listener.listener: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:listener/app/graphql-api-dev-alb/83649cc106b45569/9c7828bc7aa6e6a5]
aws_ecs_task_definition.definition: Drift detected (update)
aws_cloudwatch_log_group.log_group: Drift detected (update)
aws_iam_policy.fargate_policy: Drift detected (update)
aws_ecs_cluster.cluster: Drift detected (update)
aws_lb.alb: Drift detected (update)
aws_ecs_service.service: Drift detected (update)
aws_subnet.subnet["us-east-1b"]: Drift detected (update)
aws_subnet.subnet["us-east-1d"]: Drift detected (update)
aws_default_route_table.default: Drift detected (update)
aws_iam_role.ecs_task_execution_role: Drift detected (update)
aws_lb_target_group.target_group: Drift detected (update)
aws_lb_listener.listener: Drift detected (update)
aws_security_group.graphql_api: Drift detected (update)
aws_default_vpc.vpc: Drift detected (update)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # aws_ecs_service.service will be updated in-place
  ~ resource "aws_ecs_service" "service" {
        id                                 = "arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc"
        name                               = "graphql-api-dev-svc"
        tags                               = {}
      ~ task_definition                    = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task:2" -> (known after apply)
        # (15 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

  # aws_ecs_task_definition.definition must be replaced
-/+ resource "aws_ecs_task_definition" "definition" {
      ~ arn                      = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task:2" -> (known after apply)
      ~ arn_without_revision     = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task" -> (known after apply)
      ~ container_definitions    = jsonencode(
          ~ [
              ~ {
                  ~ image            = "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:cfdb9a63dd992253a6e627b7f75c9107f6ab9b30" -> "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:05c263e83f2f3c330254a0afcb5deb218cc1a662"
                    name             = "graphql-api-dev-container"
                    # (8 unchanged attributes hidden)
                },
            ] # forces replacement
        )
      ~ id                       = "graphql-api-dev-task" -> (known after apply)
      ~ revision                 = 2 -> (known after apply)
      - tags                     = {} -> null
      ~ tags_all                 = {} -> (known after apply)
        # (7 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 1 to add, 1 to change, 1 to destroy.

Pushed by: @renovate[bot], Action: pull_request, Environment: dev

[github-actions]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖success

Show Plan

terraform
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/CrimLog/dev/runs/run-i2BJjVeRg9jUYiT8

Waiting for the plan to start...

Terraform v1.4.5
on linux_amd64
Initializing plugins and modules...
aws_iam_policy.fargate_policy: Refreshing state... [id=arn:aws:iam::043894507808:policy/graphql-api-dev-fargate-policy]
aws_cloudwatch_log_group.log_group: Refreshing state... [id=/ecs/graphql-api-dev]
aws_iam_role.ecs_task_execution_role: Refreshing state... [id=graphql-api-dev-execution-role]
data.aws_acm_certificate.cert: Refreshing...
aws_ecs_cluster.cluster: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:cluster/graphql-api-dev]
aws_default_vpc.vpc: Refreshing state... [id=vpc-0d6048d87526ca2aa]
aws_vpc.vpc: Refreshing state... [id=vpc-0dd1abc04eb78546a]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment2: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451372400000001]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment1: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451387600000002]
aws_ecs_task_definition.definition: Refreshing state... [id=graphql-api-dev-task]
data.aws_acm_certificate.cert: Refresh complete after 0s [id=arn:aws:acm:us-east-1:043894507808:certificate/bf306bea-c739-451e-bc54-bfd24909b37c]
aws_internet_gateway.gw: Refreshing state... [id=igw-0f722e2ec075b406a]
aws_vpc_peering_connection.peering_connection: Refreshing state... [id=pcx-02ca43ff46d27f622]
aws_subnet.subnet["us-east-1b"]: Refreshing state... [id=subnet-068e99669610bf988]
aws_security_group.graphql_api: Refreshing state... [id=sg-0cead3059c486959e]
aws_subnet.subnet["us-east-1d"]: Refreshing state... [id=subnet-0699b39f84d929a68]
aws_lb_target_group.target_group: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:targetgroup/graphql-api-dev/83e131544a9b44d8]
aws_default_security_group.default: Refreshing state... [id=sg-061747dff8a994e8b]
aws_security_group.web_everyone2: Refreshing state... [id=sg-0ceb37cfb20b50043]
aws_lb.alb: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:loadbalancer/app/graphql-api-dev-alb/252731848262f1ac]
aws_route.vpc_peering_route: Refreshing state... [id=r-rtb-09b02ae3a536a3f7a2811395018]
aws_default_route_table.default: Refreshing state... [id=rtb-0209f8b11e4513cc2]
aws_ecs_service.service: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc]
aws_lb_listener.listener: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:listener/app/graphql-api-dev-alb/252731848262f1ac/cee2a346a2c2a344]
aws_security_group.graphql_api: Drift detected (update)
aws_iam_policy.fargate_policy: Drift detected (update)
aws_ecs_task_definition.definition: Drift detected (update)
aws_lb.alb: Drift detected (update)
aws_ecs_service.service: Drift detected (update)
aws_cloudwatch_log_group.log_group: Drift detected (update)
aws_subnet.subnet["us-east-1b"]: Drift detected (update)
aws_subnet.subnet["us-east-1d"]: Drift detected (update)
aws_ecs_cluster.cluster: Drift detected (update)
aws_iam_role.ecs_task_execution_role: Drift detected (update)
aws_default_route_table.default: Drift detected (update)
aws_default_vpc.vpc: Drift detected (update)
aws_lb_listener.listener: Drift detected (update)
aws_lb_target_group.target_group: Drift detected (update)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # aws_ecs_service.service will be updated in-place
  ~ resource "aws_ecs_service" "service" {
        id                                 = "arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc"
        name                               = "graphql-api-dev-svc"
        tags                               = {}
      ~ task_definition                    = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task:3" -> (known after apply)
        # (15 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

  # aws_ecs_task_definition.definition must be replaced
-/+ resource "aws_ecs_task_definition" "definition" {
      ~ arn                      = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task:3" -> (known after apply)
      ~ arn_without_revision     = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task" -> (known after apply)
      ~ container_definitions    = jsonencode(
          ~ [
              ~ {
                  ~ image            = "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:ea0cbb6f1af2b62f18d904183442047872313923" -> "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:b640c52de0bb72973904815542ad5931cc8e3d10"
                    name             = "graphql-api-dev-container"
                    # (8 unchanged attributes hidden)
                },
            ] # forces replacement
        )
      ~ id                       = "graphql-api-dev-task" -> (known after apply)
      ~ revision                 = 3 -> (known after apply)
      - tags                     = {} -> null
      ~ tags_all                 = {} -> (known after apply)
        # (7 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 1 to add, 1 to change, 1 to destroy.

Pushed by: @renovate[bot], Action: pull_request, Environment: dev

[github-actions]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖success

Show Plan

terraform
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/CrimLog/dev/runs/run-jaeNTd9NqoP1C3my

Waiting for the plan to start...

Terraform v1.4.5
on linux_amd64
Initializing plugins and modules...
aws_cloudwatch_log_group.log_group: Refreshing state... [id=/ecs/graphql-api-dev]
aws_iam_policy.fargate_policy: Refreshing state... [id=arn:aws:iam::043894507808:policy/graphql-api-dev-fargate-policy]
aws_vpc.vpc: Refreshing state... [id=vpc-0dd1abc04eb78546a]
aws_iam_role.ecs_task_execution_role: Refreshing state... [id=graphql-api-dev-execution-role]
aws_default_vpc.vpc: Refreshing state... [id=vpc-0d6048d87526ca2aa]
data.aws_acm_certificate.cert: Refreshing...
aws_ecs_cluster.cluster: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:cluster/graphql-api-dev]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment1: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451387600000002]
aws_ecs_task_definition.definition: Refreshing state... [id=graphql-api-dev-task]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment2: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451372400000001]
data.aws_acm_certificate.cert: Refresh complete after 0s [id=arn:aws:acm:us-east-1:043894507808:certificate/bf306bea-c739-451e-bc54-bfd24909b37c]
aws_security_group.graphql_api: Refreshing state... [id=sg-0cead3059c486959e]
aws_subnet.subnet["us-east-1d"]: Refreshing state... [id=subnet-0699b39f84d929a68]
aws_subnet.subnet["us-east-1b"]: Refreshing state... [id=subnet-068e99669610bf988]
aws_internet_gateway.gw: Refreshing state... [id=igw-0f722e2ec075b406a]
aws_default_security_group.default: Refreshing state... [id=sg-061747dff8a994e8b]
aws_lb_target_group.target_group: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:targetgroup/graphql-api-dev/83e131544a9b44d8]
aws_security_group.web_everyone2: Refreshing state... [id=sg-0ceb37cfb20b50043]
aws_lb.alb: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:loadbalancer/app/graphql-api-dev-alb/252731848262f1ac]
aws_ecs_service.service: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc]
aws_vpc_peering_connection.peering_connection: Refreshing state... [id=pcx-02ca43ff46d27f622]
aws_route.vpc_peering_route: Refreshing state... [id=r-rtb-09b02ae3a536a3f7a2811395018]
aws_default_route_table.default: Refreshing state... [id=rtb-0209f8b11e4513cc2]
aws_lb_listener.listener: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:listener/app/graphql-api-dev-alb/252731848262f1ac/cee2a346a2c2a344]
aws_ecs_task_definition.definition: Drift detected (update)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # aws_ecs_service.service will be updated in-place
  ~ resource "aws_ecs_service" "service" {
        id                                 = "arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc"
        name                               = "graphql-api-dev-svc"
        tags                               = {}
      ~ task_definition                    = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task:4" -> (known after apply)
        # (15 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

  # aws_ecs_task_definition.definition must be replaced
-/+ resource "aws_ecs_task_definition" "definition" {
      ~ arn                      = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task:4" -> (known after apply)
      ~ arn_without_revision     = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task" -> (known after apply)
      ~ container_definitions    = jsonencode(
          ~ [
              ~ {
                  ~ image            = "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:dc3cf63d0d9c0cabcada061e5c39ebc628fe79cf" -> "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:3d3fa27483964813f97b404e74979983545ae111"
                    name             = "graphql-api-dev-container"
                    # (8 unchanged attributes hidden)
                },
            ] # forces replacement
        )
      ~ id                       = "graphql-api-dev-task" -> (known after apply)
      ~ revision                 = 4 -> (known after apply)
      - tags                     = {} -> null
      ~ tags_all                 = {} -> (known after apply)
        # (7 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 1 to add, 1 to change, 1 to destroy.

Pushed by: @renovate[bot], Action: pull_request, Environment: dev

[github-actions]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖success

Show Plan

terraform
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/CrimLog/dev/runs/run-8QnBzXr8WmerJ6DF

Waiting for the plan to start...

Terraform v1.4.5
on linux_amd64
Initializing plugins and modules...
data.aws_acm_certificate.cert: Refreshing...
aws_default_vpc.vpc: Refreshing state... [id=vpc-0d6048d87526ca2aa]
aws_cloudwatch_log_group.log_group: Refreshing state... [id=/ecs/graphql-api-dev]
aws_ecs_cluster.cluster: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:cluster/graphql-api-dev]
aws_iam_role.ecs_task_execution_role: Refreshing state... [id=graphql-api-dev-execution-role]
aws_iam_policy.fargate_policy: Refreshing state... [id=arn:aws:iam::043894507808:policy/graphql-api-dev-fargate-policy]
aws_vpc.vpc: Refreshing state... [id=vpc-0dd1abc04eb78546a]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment1: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451387600000002]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment2: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451372400000001]
aws_ecs_task_definition.definition: Refreshing state... [id=graphql-api-dev-task]
data.aws_acm_certificate.cert: Refresh complete after 1s [id=arn:aws:acm:us-east-1:043894507808:certificate/bf306bea-c739-451e-bc54-bfd24909b37c]
aws_internet_gateway.gw: Refreshing state... [id=igw-0f722e2ec075b406a]
aws_subnet.subnet["us-east-1d"]: Refreshing state... [id=subnet-0699b39f84d929a68]
aws_vpc_peering_connection.peering_connection: Refreshing state... [id=pcx-02ca43ff46d27f622]
aws_security_group.graphql_api: Refreshing state... [id=sg-0cead3059c486959e]
aws_security_group.web_everyone2: Refreshing state... [id=sg-0ceb37cfb20b50043]
aws_subnet.subnet["us-east-1b"]: Refreshing state... [id=subnet-068e99669610bf988]
aws_lb_target_group.target_group: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:targetgroup/graphql-api-dev/83e131544a9b44d8]
aws_default_security_group.default: Refreshing state... [id=sg-061747dff8a994e8b]
aws_route.vpc_peering_route: Refreshing state... [id=r-rtb-09b02ae3a536a3f7a2811395018]
aws_default_route_table.default: Refreshing state... [id=rtb-0209f8b11e4513cc2]
aws_lb.alb: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:loadbalancer/app/graphql-api-dev-alb/252731848262f1ac]
aws_ecs_service.service: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc]
aws_lb_listener.listener: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:listener/app/graphql-api-dev-alb/252731848262f1ac/cee2a346a2c2a344]
aws_ecs_task_definition.definition: Drift detected (update)

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # aws_ecs_service.service will be updated in-place
  ~ resource "aws_ecs_service" "service" {
        id                                 = "arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc"
        name                               = "graphql-api-dev-svc"
        tags                               = {}
      ~ task_definition                    = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task:4" -> (known after apply)
        # (15 unchanged attributes hidden)

        # (4 unchanged blocks hidden)
    }

  # aws_ecs_task_definition.definition must be replaced
-/+ resource "aws_ecs_task_definition" "definition" {
      ~ arn                      = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task:4" -> (known after apply)
      ~ arn_without_revision     = "arn:aws:ecs:us-east-1:043894507808:task-definition/graphql-api-dev-task" -> (known after apply)
      ~ container_definitions    = jsonencode(
          ~ [
              ~ {
                  ~ image            = "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:dc3cf63d0d9c0cabcada061e5c39ebc628fe79cf" -> "043894507808.dkr.ecr.us-east-1.amazonaws.com/graphql-api:daff4056146a7408343ae6d92defa44aa3f5eb79"
                    name             = "graphql-api-dev-container"
                    # (8 unchanged attributes hidden)
                },
            ] # forces replacement
        )
      ~ id                       = "graphql-api-dev-task" -> (known after apply)
      ~ revision                 = 4 -> (known after apply)
      - tags                     = {} -> null
      ~ tags_all                 = {} -> (known after apply)
        # (7 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 1 to add, 1 to change, 1 to destroy.

Pushed by: @renovate[bot], Action: pull_request, Environment: dev

[github-actions]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖failure

Show Plan

terraform
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/CrimLog/dev/runs/run-RoHKFr2dutpnAD4N

Waiting for the plan to start...

Terraform v1.4.5
on linux_amd64
Initializing plugins and modules...
aws_iam_policy.fargate_policy: Refreshing state... [id=arn:aws:iam::043894507808:policy/graphql-api-dev-fargate-policy]
aws_default_vpc.vpc: Refreshing state... [id=vpc-0d6048d87526ca2aa]
aws_vpc.vpc: Refreshing state... [id=vpc-0dd1abc04eb78546a]
aws_iam_role.ecs_task_execution_role: Refreshing state... [id=graphql-api-dev-execution-role]
aws_ecs_cluster.cluster: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:cluster/graphql-api-dev]
data.aws_acm_certificate.cert: Refreshing...
aws_cloudwatch_log_group.log_group: Refreshing state... [id=/ecs/graphql-api-dev]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment2: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451372400000001]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment1: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451387600000002]
aws_default_security_group.default: Refreshing state... [id=sg-061747dff8a994e8b]
aws_security_group.graphql_api: Refreshing state... [id=sg-0cead3059c486959e]
aws_internet_gateway.gw: Refreshing state... [id=igw-0f722e2ec075b406a]
aws_subnet.subnet["us-east-1d"]: Refreshing state... [id=subnet-0699b39f84d929a68]
aws_lb_target_group.target_group: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:targetgroup/graphql-api-dev/83e131544a9b44d8]
aws_security_group.web_everyone2: Refreshing state... [id=sg-0ceb37cfb20b50043]
aws_subnet.subnet["us-east-1b"]: Refreshing state... [id=subnet-068e99669610bf988]
aws_vpc_peering_connection.peering_connection: Refreshing state... [id=pcx-02ca43ff46d27f622]
aws_ecs_task_definition.definition: Refreshing state... [id=graphql-api-dev-task]
aws_route.vpc_peering_route: Refreshing state... [id=r-rtb-09b02ae3a536a3f7a2811395018]
aws_lb.alb: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:loadbalancer/app/graphql-api-dev-alb/252731848262f1ac]
aws_default_route_table.default: Refreshing state... [id=rtb-0209f8b11e4513cc2]
aws_ecs_service.service: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc]
data.aws_acm_certificate.cert: Still refreshing... [10s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [20s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [30s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [40s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [50s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [1m0s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [1m10s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [1m20s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [1m30s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [1m40s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [1m50s elapsed]
data.aws_acm_certificate.cert: Still refreshing... [2m0s elapsed]
aws_lb.alb: Drift detected (delete)
aws_security_group.web_everyone2: Drift detected (delete)
aws_route.vpc_peering_route: Drift detected (delete)
aws_internet_gateway.gw: Drift detected (delete)
aws_subnet.subnet["us-east-1b"]: Drift detected (delete)
aws_subnet.subnet["us-east-1d"]: Drift detected (delete)
aws_default_route_table.default: Drift detected (delete)
aws_ecs_cluster.cluster: Drift detected (delete)
aws_security_group.graphql_api: Drift detected (delete)
aws_ecs_service.service: Drift detected (delete)
aws_vpc_peering_connection.peering_connection: Drift detected (delete)
aws_default_vpc.vpc: Drift detected (delete)
aws_vpc.vpc: Drift detected (delete)
aws_default_security_group.default: Drift detected (delete)
aws_ecs_task_definition.definition: Drift detected (update)
╷
│ Error: no certificate for domain "crimlog.org" found in this Region
│
│   with data.aws_acm_certificate.cert,
│   on lb.tf line 51, in data "aws_acm_certificate" "cert":
│   51: data "aws_acm_certificate" "cert" {
│
╵
Operation failed: failed running terraform plan (exit 1)

Pushed by: @renovate[bot], Action: pull_request, Environment: dev

[github-actions]

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖success

Terraform Plan 📖failure

Show Plan

terraform
Running plan in Terraform Cloud. Output will stream here. Pressing Ctrl-C
will stop streaming the logs, but will not stop the plan running remotely.

Preparing the remote plan...

To view this run in a browser, visit:
https://app.terraform.io/app/CrimLog/dev/runs/run-QCsAGkrG79LvGTyZ

Waiting for the plan to start...

Terraform v1.4.5
on linux_amd64
Initializing plugins and modules...
data.aws_acm_certificate.cert: Refreshing...
aws_cloudwatch_log_group.log_group: Refreshing state... [id=/ecs/graphql-api-dev]
aws_iam_policy.fargate_policy: Refreshing state... [id=arn:aws:iam::043894507808:policy/graphql-api-dev-fargate-policy]
aws_ecs_cluster.cluster: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:cluster/graphql-api-dev]
aws_default_vpc.vpc: Refreshing state... [id=vpc-0d6048d87526ca2aa]
aws_iam_role.ecs_task_execution_role: Refreshing state... [id=graphql-api-dev-execution-role]
aws_vpc.vpc: Refreshing state... [id=vpc-0dd1abc04eb78546a]
aws_internet_gateway.gw: Refreshing state... [id=igw-0f722e2ec075b406a]
aws_default_security_group.default: Refreshing state... [id=sg-061747dff8a994e8b]
aws_subnet.subnet["us-east-1d"]: Refreshing state... [id=subnet-0699b39f84d929a68]
aws_subnet.subnet["us-east-1b"]: Refreshing state... [id=subnet-068e99669610bf988]
aws_security_group.web_everyone2: Refreshing state... [id=sg-0ceb37cfb20b50043]
aws_vpc_peering_connection.peering_connection: Refreshing state... [id=pcx-02ca43ff46d27f622]
aws_lb_target_group.target_group: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:targetgroup/graphql-api-dev/83e131544a9b44d8]
aws_security_group.graphql_api: Refreshing state... [id=sg-0cead3059c486959e]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment2: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451372400000001]
aws_ecs_task_definition.definition: Refreshing state... [id=graphql-api-dev-task]
aws_iam_role_policy_attachment.ecs-task-execution-role-policy-attachment1: Refreshing state... [id=graphql-api-dev-execution-role-20230428144451387600000002]
aws_route.vpc_peering_route: Refreshing state... [id=r-rtb-09b02ae3a536a3f7a2811395018]
aws_default_route_table.default: Refreshing state... [id=rtb-0209f8b11e4513cc2]
aws_lb.alb: Refreshing state... [id=arn:aws:elasticloadbalancing:us-east-1:043894507808:loadbalancer/app/graphql-api-dev-alb/252731848262f1ac]
aws_ecs_service.service: Refreshing state... [id=arn:aws:ecs:us-east-1:043894507808:service/graphql-api-dev/graphql-api-dev-svc]
aws_lb.alb: Drift detected (delete)
aws_security_group.graphql_api: Drift detected (delete)
aws_ecs_task_definition.definition: Drift detected (update)
aws_ecs_cluster.cluster: Drift detected (delete)
aws_default_vpc.vpc: Drift detected (delete)
aws_vpc_peering_connection.peering_connection: Drift detected (delete)
aws_internet_gateway.gw: Drift detected (delete)
aws_default_security_group.default: Drift detected (delete)
aws_route.vpc_peering_route: Drift detected (delete)
aws_ecs_service.service: Drift detected (delete)
aws_security_group.web_everyone2: Drift detected (delete)
aws_vpc.vpc: Drift detected (delete)
aws_default_route_table.default: Drift detected (delete)
aws_subnet.subnet["us-east-1b"]: Drift detected (delete)
aws_subnet.subnet["us-east-1d"]: Drift detected (delete)
╷
│ Error: no certificate for domain "crimlog.org" found in this Region
│
│   with data.aws_acm_certificate.cert,
│   on lb.tf line 51, in data "aws_acm_certificate" "cert":
│   51: data "aws_acm_certificate" "cert" {
│
╵
Operation failed: failed running terraform plan (exit 1)

Pushed by: @renovate[bot], Action: pull_request, Environment: dev