Conversation
…tions Bind project actions, workspace requests, logs, and permission gates to the owning environment. Preserve selected project objects across pagination for bulk operations. AI assistance: implemented with OpenAI Codex. Formatting and frontend, tests, and email type checks passed. Repository-wide lint timed out loading backend packages under memory limits. Human deployment and manual verification pending.
|
What you referring to is the small stesp ive been taking to get it to. place to show all resources, Ive been slowly trying to get it to a place where it can show everytihng however, the fatest way and most efficent way is going to be a push based agent, which will include breaking changes, i have a branch locally with a idea, but its taking me alot longer to work on it then i have free time. |
|
Im open to see your idea, but just inclduing everything in the frontned is not up to par with what i would like arcane to be, As for all intensive purposes javascript is slow, while go is fast |
|
Makes sense, I haven't looked at the agent side. The UI changes in this PR are more light touch than your vision and leverage the current backend API as is. Aim was to suggest an approach to unify the views around projects, containers, etc. but not require an updated agent resource model. I'm open to taking a look at that if you're willing to share the branch? |
|
I took a quick look, I think I understand your concern - the api is pulling from every host on certain page loads which won't scale. |
|
Like I said feel free to lay ground work for it, any help is welcome, just I want it to be seamless and just waiting on api calls |
|
This pull request has merge conflicts. Please resolve the conflicts so the PR can stay up-to-date and reviewed. |
…0912 Add Hyperion agent operating policy
2 participants
Arcane seems to have split UX philosophy, with Dashboard presenting a global view of all environments but then updates/projects/container etc. pages are scoped to a single environment selected in the left-hand bar. It seems having a global environment view would be useful - allowing all resources e.g. containers, images, networks, to be visible in a single pane. This 'Global' option should live alongside current scoped behaviour as a selected option in the environment picker.
However, the main barrier to that is that objects do not currently carry their environmentId in views such as Projects (relying on the selected environment value instead). This change attaches environmentId to project objects when they are fetched and passes that environment explicitly through project actions, workspace requests, logs, and related container operations.
This change focused on projects only to demonstrate the pattern, if acceptable the natural evolution would be to continue across all relevant views such that a 'global' view can be made available in the environment picker that shows everything.
This change is currently neutral, there is no added behaviour and no regression - all tests pass. User UI testing shows it behaves as expected. It is submitted for consideration and comments on overall approach and if this is or is not a direction Arcane should head in.
Validation
AI assistance
Design approach was mine. OpenAI Codex assisted with implementation and validation.