Skip to content

feat: Reach per-service settings from the CLI - #14

Open
nfebe wants to merge 1 commit into
feat/upload-limitfrom
feat/service-settings
Open

nfebe wants to merge 1 commit into
feat/upload-limitfrom
feat/service-settings

Conversation

@nfebe

@nfebe nfebe commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

Add deployments services-settings and services-settings-update.

`flatrun deployments services-settings NAME SERVICE` reads a service's saved
compose settings and `services-settings-update` replaces them, so limits,
restart policy, log rotation, environment and command can be scripted.
@sourceant

sourceant Bot commented Oct 26, 2026

Copy link
Copy Markdown

Code Review Summary

The change registers two new generated endpoint entries in the deployments family: a GET and a PUT on /deployments/:name/services/:service/settings, each taking name and service path arguments. Because the CLI derives commands from this table, it gains services-settings and services-settings-update operations for reading and updating a single service's settings. No other code paths change.

🚀 Key Improvements

  • Per-service settings become reachable from the CLI without hand-written command code, via internal/command/endpoints_gen.go.

@sourceant sourceant Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Review complete. See the overview comment for a summary.

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