Releases: inceptionstack/loki-agent
Releases · inceptionstack/loki-agent
v0.2.0-rc9
fix: add -no-color to all terraform commands so error parser works Terraform emits ANSI escape codes even when piped, which prevents parse_existing_resources from matching 'Error:' lines. Adding -no-color to init, plan, apply, output, and import commands ensures clean output for both parsing and TUI display.
v0.2.0-rc8
fix: always checkout correct tag when cached repo ref mismatches bina…
v0.2.0-rc7
fix: auto-import pre-existing AWS resources on Terraform apply failure When terraform apply fails with EntityAlreadyExists or 'already exists' errors, the adapter now: 1. Parses conflicting resources from the error output 2. Logs 'Auto-importing pre-existing resource: <addr> (<id>)' for each 3. Runs terraform import for each supported resource type 4. Re-plans and re-applies once Supported resource types: aws_iam_role, aws_iam_instance_profile, aws_s3_bucket, aws_security_group, aws_vpc. If the retry also fails, the original error is returned. Unit tests cover resource parsing, import command generation, and edge cases (unsupported types, non-creation errors).
v0.2.0-rc6
fix: truncate long artifact values and log lines in TUI deploy screen - Artifact values truncated to 80 chars in TUI sink to prevent terraform_init_output and terraform_plan_output from overflowing - Deploy screen log lines truncated to 120 chars - Show last 20 log lines instead of 12
v0.2.0-rc5
fix: async TUI deploy - spawn install in background task with live pr…
v0.2.0-rc4
fix: BASH_SOURCE stdin compat + bump version to 0.2.0-rc4 for repo sync
- install.sh: use ${BASH_SOURCE[0]:-$0} so piped execution works
- Cargo.toml version bumped to 0.2.0-rc4 so desired_repo_ref()
resolves to the correct tag when syncing the cached repo
v0.2.0-rc3
V2 installer RC3 — --for-agent JSONL output
v0.2.0-rc22
fix: unbound OPTION_ARGS with set -u on empty arrays
Bash set -u treats empty array expansion as unbound variable on
some versions. Use ${arr[@]+"${arr[@]}"} pattern for safe
expansion of potentially empty arrays.
v0.2.0-rc21
feat: bootstrap wait, SSM session doc, plugin cache, CloudShell workdir Closes 4 critical v1 parity gaps: 1. BOOTSTRAP WAIT: After terraform apply, polls SSM parameters /loki/setup-status and /loki/setup-step for up to 10 minutes. Shows live progress in TUI log. On failure, fetches error details. On success, marks instance_health as 'ready'. 2. SSM SESSION DOCUMENT: Creates 'Loki-Session' SSM document that starts sessions as ec2-user with bash login shell. Post-install screen includes --document-name in the SSM command when available. 3. TF_PLUGIN_CACHE_DIR: Sets /tmp/terraform-plugin-cache before terraform init to avoid re-downloading ~500MB of providers. 4. CLOUDSHELL WORKDIR: Checks available disk space before init. If <600MB available on CloudShell, copies terraform workdir to /tmp and continues from there (matching v1 behavior). Also: added env field to CommandSpec for per-command environment variables. Updated CFN adapter for compatibility.
v0.2.0-rc20
fix: address Codex review — 6 fixes for v2 installer Based on full review of rc11..rc19 changes: 1. ENVIRONMENT NAME PERSISTENCE: Read from terraform state first, then .loki-env file, then generate new suffix. Prevents destroying old resources on reinstall from same checkout. 2. PACK/PROFILE SELECTION: PacksLoaded and ProfilesLoaded no longer auto-chain to the next action. They set the cursor on the default and render the screen, so user can see and change the selection before pressing Enter. 3. UTF-8 SAFE TRUNCATION: Deploy screen log truncation now uses chars().take() instead of byte slicing to avoid panics on multibyte characters. 4. ARTIFACT LOG GARBLING: ArtifactRecorded values now have newlines collapsed to spaces before display. Strip \r from terraform output. 5. BEDROCK FORM: Reverted enable_satellite_services to true (security services should run on first install). Instead, gated bedrock form invoke on request_quota_increases == true (defaults to false). 6. STACK NAME IN POST-INSTALL: Record environment_name as stack_name artifact so post-install screen shows the actual deployed name.