Skip to content

Conversation

@Thorium
Copy link
Contributor

@Thorium Thorium commented Nov 4, 2025

I did ask from Claude Sonnet what is in FsCDK (AWS) that Farmer (Azure) is missing, and it came up with this PR:

  • Farmer lacks best-practice safe settings for production ready environments.
  • So this build adds those

Farmer already has some opinionated approaches, but it doesn't really go into "production-environment-focus" (cost-efficiency, logging, hardened security, and so on).

Be suspicious about agents... Meanwhile this PR can be ready for merge, I'm not actually expecting that.
Rather the question is, would we want to take Farmer into this direction or no?

@ninjarobot
Copy link
Collaborator

I had copilot do a few PR's, so no problem with that, but every change still needs to follow the requirements in the PR template. Two big areas that we have to watch for:

  • Testing against a live Azure subscription to make sure the changes really work - this falls on the human to do (or you can give an agent access to your own subscription for testing).
  • Testing for backwards compatibility. This PR didn't do it, but some PR's go and change all the breaking tests, even when the breakage is there to catch compatibility issues.

Copy link
Collaborator

@ninjarobot ninjarobot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These changes look good from the standpoint of functionality and compatibility. All the documentation is definitely appreciated as well.

@Thorium
Copy link
Contributor Author

Thorium commented Dec 5, 2025

This was rather question (with code attached) of do we want to take this direction, rather than a PR intended to be merged. We can close the PR but what you think about the idea?

@Thorium Thorium closed this Dec 5, 2025
@Thorium
Copy link
Contributor Author

Thorium commented Dec 5, 2025

Reopened: Actually, as documentation improvement, this might be valuable.

@Thorium Thorium reopened this Dec 5, 2025
@ninjarobot
Copy link
Collaborator

I'm good with the direction and I've been going through issues to see which ones are defined clearly enough to give to AI. It would definitely really help to tell it to focus on a feature at a time, though. Maintaining quality when there are huge change sets coming in from AI is really difficult. Breaking changes are incredibly detrimental to OSS projects - the last thing we want is for users to be concerned about taking upgrades.

@ninjarobot
Copy link
Collaborator

I had to do this for Copilot so it would fix up code to prevent fantomas failures. Is there something that could be added to the repo to make it easier for Claude as well?

@Thorium
Copy link
Contributor Author

Thorium commented Dec 5, 2025

Generally working with all agents, you add AGENTS.md as general instructions and patterns how they should do things. You can ask e.g. Claude to generate you a template and then modify it by your needs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants