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
The previous implementation didn't prevent migrated single-tenant
users from selecting another org than the one their project ID
belongs to, leading to confusing behaviour.
Here, if a project ID is present, we ensure that the organization ID
belonging to it (if any) is always used, and is automatically written
into the project config on disk.
Organization ID mismatch detected. The configured organizationId (${organizationId}) differs from the organization associated with the legacy project ID (${resolvedOrgId}).
77
+
78
+
Using ${resolvedOrgId} from the legacy project ID. Your project configuration will be updated automatically.
79
+
`+"\n",
80
+
})
81
+
}elseif(!organizationId){
82
+
log.warn({
83
+
msg:
84
+
dedent`
85
+
Organization ID resolved from legacy project ID. Your project configuration will be updated to include the organization ID and comment out the legacy fields (project ID and domain).
0 commit comments