Skip to content

refactor(#1109): agent env setup should not affect other envs#1128

Merged
wesleyboar merged 6 commits into
mainfrom
fix/WC-428-elasticsearch-timeout
May 27, 2026
Merged

refactor(#1109): agent env setup should not affect other envs#1128
wesleyboar merged 6 commits into
mainfrom
fix/WC-428-elasticsearch-timeout

Conversation

@wesleyboar
Copy link
Copy Markdown
Member

@wesleyboar wesleyboar commented Mar 24, 2026

Overview

Do not let A.I. agent environment tweaks affect other environments.

Related

Changes

  • ignores docker-compose.agent.yml
  • documents that AI should use docker-compose.agent.yml as necessary

Testing

Skipped.

UI

N/A

Notes

Initially, this PR was to solve WC-428, but @jarosenb assures me that the real issue (private) is unrelated to this. But, I still would have preferred this solution to #1109, so I'm tempted to merge it.

This half-reverts commit d146f57.

Do not update Elasticsearch for humans.
@wesleyboar wesleyboar requested a review from jarosenb March 24, 2026 17:33
@wesleyboar wesleyboar changed the title refactor(#1109): agent env setup should not affect humans refactor(#1109): agent env setup should not affect other envs Mar 24, 2026
@wesleyboar wesleyboar requested a review from rstijerina March 24, 2026 17:45
Comment thread AGENTS.md Outdated
@wesleyboar
Copy link
Copy Markdown
Member Author

I don't use remote agents now1, but this PR still seems good to me.

Footnotes

  1. Cursor made local agents more convenient.

@wesleyboar
Copy link
Copy Markdown
Member Author

wesleyboar commented May 27, 2026

I re-reviewed again.

Pros:

  • Reverts a change I should not have made.
  • Still supports remote agents.
  • Local and Remote servers are unaffected.

Cons: 🤷

Merging.

@wesleyboar wesleyboar merged commit f646857 into main May 27, 2026
@wesleyboar wesleyboar deleted the fix/WC-428-elasticsearch-timeout branch May 27, 2026 19:38
@wesleyboar
Copy link
Copy Markdown
Member Author

Local Core-CMS servers are affected by Elasticsearch downgrade. I'm pretty sure I'm the only one with one of those… so we're good.

If someone complains their local Core-CMS broke, point them to me or have them delete core_cms_elasticsearch volume.

A local Core-Portal would be unaffected, cuz it has its own elasticsearch.

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.

1 participant