Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,9 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]
- Fix: editing a k8s scope now runs the provider's update workflow (networking, ingress and IAM re-applied from the new settings, with step-by-step progress in the dashboard). Before, the `update-scope` action was never registered, so an edit was marked active immediately without touching the cluster. Providers configured before this version need the new action registered once: `np service specification action specification create --serviceSpecificationId <id> --body "$(gomplate --file k8s/specs/actions/update-scope.json.tpl)"` with `SERVICE_SPECIFICATION_ID` set, or re-run `./configure`

## [1.16.1] - 2026-09-02
- Fix: the Instances tab of the performance view now shows every pod of a k8s scope. The instance list had a hard cap of 10 that nothing could override, so a scope with 20 pods showed only the first 10 and the table had no next page. A `limit` in the request is honored, the `LIMIT` env var on the agent stays as the operator override, and with neither every pod is returned

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ Run the configuration script to register the scope schema, actions, and the agen

The script will:
- Register the JSON schema for the selected scope (from `$SERVICE_PATH`).
- Create action specifications (e.g., `create-scope`, `delete-scope`).
- Create action specifications (e.g., `create-scope`, `update-scope`, `delete-scope`).
- Register the scope type.
- Set up a notification channel for your agent.

Expand Down
29 changes: 29 additions & 0 deletions k8s/specs/actions/update-scope.json.tpl
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
{
"name": "update-scope",
"slug": "update-scope",
"type": "update",
"retryable": false,
"service_specification_id": "{{ env.Getenv "SERVICE_SPECIFICATION_ID" }}",
"parameters": {
"schema": {
"type": "object",
"required": [
"scope_id"
],
"properties": {
"scope_id": {
"type": "string"
}
}
},
"values": {}
},
"results": {
"schema": {
"type": "object",
"required": [],
"properties": {}
},
"values": {}
}
}
1 change: 1 addition & 0 deletions k8s/specs/service-spec.json.tpl
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
{
"available_actions": [
"create-scope",
"update-scope",
"delete-scope",
"start-initial",
"start-blue-green",
Expand Down
Loading