Prepare release 0.4.0 - #97
Conversation
ac428d1 to
e617346
Compare
|
|
||
| * Adds the `harness exec` command, which lets a human grant session-scoped, noninteractive `tfctl` delete permissions to a wrapped command (such as a coding agent) via `--allow-delete`. The grant is tied to all subprocesses. | ||
|
|
||
| NOTES: |
There was a problem hiding this comment.
I think notes should go at the end
|
|
||
| NOTES: | ||
|
|
||
| * Running tfctl automatically updates outdated tfctl skills that it installed unless they were modified. |
There was a problem hiding this comment.
The version/update check is under ENHANCEMENTS, but the skill auto-migration is under NOTES I find them to be similar, should we put them both in the same section?
|
|
||
| NEW FEATURES: | ||
|
|
||
| * Adds the `harness exec` command, which lets a human grant session-scoped, noninteractive `tfctl` delete permissions to a wrapped command (such as a coding agent) via `--allow-delete`. The grant is tied to all subprocesses. |
There was a problem hiding this comment.
I find the last sentence a bit ambigious.
Tell me what u think about something like:
"Adds the harness exec command, which lets a human grant session-scoped, noninteractive tfctl delete permissions to a wrapped command (such as a coding agent) by naming resource types explicitly with --allow-delete (e.g. --allow-delete=workspaces,vars). The grant lasts only for that command's session and applies to all of its subprocesses."
to make it explicitly known its class only
|
|
||
| * Using `profile display --markdown` no longer produces an error. | ||
|
|
||
| * Removed Token property from json output when using `profile profiles list --json`, preventing accidental exposure. |
There was a problem hiding this comment.
nit: tenses and structure are off relative to the other entries. I suggest chaning to "Remove", JSON output not json, lowercase token
|
|
||
| * Removed Token property from json output when using `profile profiles list --json`, preventing accidental exposure. | ||
|
|
||
| * Don't attempt to retry telemetry transmission on server errors, like rate limiting 429 errors. |
There was a problem hiding this comment.
The code disables all SDK telemetry retries, not just server errors. How is:
"Don't retry telemetry transmission on failure, including rate-limiting (429) responses."
|
|
||
| * Positional arguments and API path parameters are now checked for basic input hygiene, rejecting control characters and invalid UTF-8. This keeps malformed values out of requests and out of terminal/audit output. This is not a security boundary; authorization is still enforced by your API token. | ||
|
|
||
| * The config directory can now be overridden with the TFCTL_CONFIG_DIR environment variable. Profiles and exec sessions both resolve against this directory, making it easy to isolate tfctl state (for example, in CI or eval harnesses). |
There was a problem hiding this comment.
nit: tfctl version / tfctl --version (line 13), TFCTL_CONFIG_DIR (line 19), api (line 41) should be in backticks like the flags elsewhere
2 participants
Description
Combined the latest and beta CHANGELOG
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.