Conversation
beebauman
enabled auto-merge
September 3, 2026 03:17
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
Sep 3, 2026
beebauman
enabled auto-merge
September 3, 2026 03:46
…ntial The wizard's AWS step wrote the access-key pair to this machine, proved it with a caller-identity probe, and reported the credential saved — while the connected universe gained no aws-admin row at all. `/yoke onboard` then read `projects.capability.has` as false and told the operator to re-enter two secrets that were already on disk. The row could not be written where the credential is collected, because the project does not exist yet at that point. Apply is the first moment both facts are available, so it registers the row there beside the hosting posture, from the same region and account the verified screen showed. It writes through the settings merge, which creates an absent capability and CAS-updates a present one, so a second wizard run converges instead of refusing. Telling the halves apart is now a command rather than a guess: `yoke aws admin-status` reads the capability row through the control plane and the credential pair through the same path function the resolver reads values with, then names the missing half and only the command that fills it. The onboard hosting step reads that before asking for anything, so a saved pair is never requested twice. Two runs also guessed `--key`/`--value` on capability-settings, which takes neither: settings are one JSON document per capability. The skill taught that shape, so it now teaches the settings merge that exists, and the adapters refuse the flag pair by naming the scalar write, the aggregate read, and the secret surface `--key` actually belongs to.
The onboarding report builder carried the project half of Apply — the handoff report, the hosting posture, and the aws-admin capability row — as three tails on an already long function, pushing the module past the authored-file limit. All three are gated by the same machine-only condition and are meaningless apart from one another, so they move together into a module that owns that one job.
The rebase carried the AWS CLI preflight adapter and this branch's admin-status adapter into one tree, so the rendered inventory has to name both and count them together.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Item branch for YOK-2782; lands through the merge queue's merge_group integration gate.