Provider is not CaC aware.

[stevencl840]

Describe the bug It is possible to use the Octopus Deploy Terraform Provider to modify a Project stored in Git, but this results in an inconsistent project state.

Steps to reproduce

1. Create a new Project via Terraform
2. Convert the project to be Version Controlled
3. Use Terraform to create a new variable for the project
4. Check the database and see that the variable has been added to the database/

Expected behavior I would expect the provider to reject any request to update a project that is stored in version control.

Logs and other supporting information

Screenshots

Environment and versions:

• OS: Windows
• Octopus Server Version: 2024.3.7062
• Terraform Version: v1.9.2
• Octopus Terraform Provider Version: 0.22.1

Additional context Add any other context about the problem here.

[OzoneNZ]

Curious how this would work in practice - we extensively use VCS and the Terraform provider in conjunction with each other, as VCS is limited to deployment processes/project variables and the like, while we use Terraform to fill in the gaps such as Channels.

If this were to be implemented and VCS projects were locked off from any modifications via the Terraform provider, I'd be pretty devastated if it couldn't be opted out of :(