Skip to content

KC-1401: Require ownership before adopting service Docker setup folders and apps - #2285

Merged
craiglurey merged 1 commit into
releasefrom
fix/service-setup-ownership-check
Aug 12, 2026
Merged

KC-1401: Require ownership before adopting service Docker setup folders and apps#2285
craiglurey merged 1 commit into
releasefrom
fix/service-setup-ownership-check

Conversation

@amangalampalli-ks

Copy link
Copy Markdown
Contributor

Summary

  • Service Docker and integration setup adopted shared folders, KSM apps, and config records by hardcoded name with no ownership check, so a shared same-name folder could receive the operator’s credentials.
  • Setup now only reuses objects owned by the current account; non-owned name matches are skipped and a new owned object is created.

Changes

  • Gate folder, KSM app, and config-record adoption in the shared Docker setup base on ownership.
  • Apply the same ownership checks to integration folder/record lookup on re-run.
  • Allow forced KSM app create when a non-owned same-title app would otherwise block setup.
  • Add unit tests for squat skip, owned preference, and create fallback.

…ps (#2281)

* Require ownership before adopting service Docker setup folders and apps

* Use folder_add instead of mkdir to create duplicate name share folder
@amangalampalli-ks amangalampalli-ks self-assigned this Aug 12, 2026
@amangalampalli-ks
amangalampalli-ks marked this pull request as ready for review August 12, 2026 12:12
@craiglurey
craiglurey merged commit ee2ef12 into release Aug 12, 2026
4 checks passed
@sk-keeper
sk-keeper deleted the fix/service-setup-ownership-check branch August 12, 2026 15:27
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.

2 participants