You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a74b173
Browse filesBrowse the repository at this point in the historyBrowse files
fix: an already-shared connection is not rewritten without --share, and every result after such a rewrite says who can use it
- the connection's own privacy is read from the connections list; anything but "private" (or none) needs --share before the in-place update
- the refusal names update <id> --share or sync <id> --share
- a secondary connection promoted to an entry's default needs --share
- sync step labels, attach-only sync and failure results report the audience
- CLI --share wiring and connect's JSON shared are tested
Co-Authored-By: Claude Opus 5.5 <[email protected]>
// An update in place hands the new credential to everyone the connection is already shared with, so it needs the same consent as attaching to a shared workspace.
`the workspace connection is shared with other people, so updating it would let them use the new credential; nothing was changed. Run altimate integrations ${command}${id} --share to update it`
1015
+
1016
+
/** Appended to what a sync or connect reports when other people can use the connection. */
1017
+
exportconstSHARED_AUDIENCE="; its members can use this connection"
1018
+
exportconstSHARED_CONNECTION_AUDIENCE="; the people it is shared with can use the new credential"
1019
+
/** Added to a failure after a shared connection was rewritten, so the text says who already has the new credential. */
1020
+
exportconstSHARED_REWRITE_NOTE=`The shared connection was updated${SHARED_CONNECTION_AUDIENCE}.`
`workspace "${name}" is shared, so attaching would let its members use this connection; it stays saved to your account only. Run altimate integrations sync ${id} --share to attach it`
1010
1024
@@ -1031,8 +1045,11 @@ async function attachToWorkspace(cfg: backend.BackendConfig, id: ProviderId, con
// Attaching widens the connection to the workspace's audience, so a workspace that does not say it is private (in this latest read) only gets it
1033
1047
// when asked. Members can use it only when the entry ends up naming it: a connection already there widens nothing more, and neither does an entry kept on another one.
if("attached"inw)step(w.kept ? `Kept the workspace's existing connection in ${workspaceLabel(w.attached,w.workspaceId)}` : `Attached to ${workspaceLabel(w.attached,w.workspaceId)}`)
// Nothing local to upload, but a connection already in the workspace may still need attaching to it: the one this machine saved, or one it has no record of.
// An existing connection was updated in place and cannot be reverted, so it stays marked rejected for update to fix; the local copy of a local credential is untouched.
0 commit comments