@Marvin are prefect profiles meant to be checked in or should they only be used for local development?

local development!

Prefect profiles are intended to store your preferred settings locally and allow you to switch between different configuration groups. These profiles are typically stored on your local machine in a file (like

profiles.toml

), which means they are designed primarily for use in local development rather than for being checked into version control systems. Here's a brief breakdown of how profiles work: 1. Local Storage: Profiles store settings on your local machine. In Prefect 2.x and 3.x, the default location is often a TOML file at

~/.prefect/profiles.toml

. 2. Configuration Flexibility: They allow easy switching between configurations, like moving between a self-hosted Prefect server and Prefect Cloud. 3. Not Typically Checked In: Since they often contain environment-specific settings, they are usually not checked into version control to avoid sharing sensitive information like API keys or environment-specific configurations. If you want more detailed information, you can look into Prefect's documentation for Prefect 2.x settings and Prefect 3.x profiles settings to understand how these profiles work in each version.