1"use strict";(self.webpackChunktigera_docs=self.webpackChunktigera_docs||[]).push([["1870"],{50343:function(e,c,t){t.r(c),t.d(c,{default:()=>h,frontMatter:()=>i,metadata:()=>n,assets:()=>r,toc:()=>s,contentTitle:()=>l});var n=JSON.parse('{"id":"reference/clis/calicoctl/datastore/migrate/unlock","title":"calicoctl datastore migrate unlock","description":"Command and options for unlocking a datastore after migration.","source":"@site/calico-enterprise_versioned_docs/version-3.17/reference/clis/calicoctl/datastore/migrate/unlock.mdx","sourceDirName":"reference/clis/calicoctl/datastore/migrate","slug":"/reference/clis/calicoctl/datastore/migrate/unlock","permalink":"/calico-enterprise/3.17/reference/clis/calicoctl/datastore/migrate/unlock","draft":false,"unlisted":false,"editUrl":"https://github.com/tigera/docs/edit/main/calico-enterprise_versioned_docs/version-3.17/reference/clis/calicoctl/datastore/migrate/unlock.mdx","tags":[],"version":"3.17","frontMatter":{"description":"Command and options for unlocking a datastore after migration."},"sidebar":"calicoEnterpriseSidebar","previous":{"title":"calicoctl datastore migrate lock","permalink":"/calico-enterprise/3.17/reference/clis/calicoctl/datastore/migrate/lock"},"next":{"title":"calicoctl label","permalink":"/calico-enterprise/3.17/reference/clis/calicoctl/label"}}'),o=t("85893"),a=t("50065");let i={description:"Command and options for unlocking a datastore after migration."},l="calicoctl datastore migrate unlock",r={},s=[{value:"Display the help text for 'calicoctl datastore migrate unlock' command",id:"display-the-help-text-for-calicoctl-datastore-migrate-unlock-command",level:2},{value:"Examples",id:"examples",level:3},{value:"General options",id:"general-options",level:3},{value:"See also",id:"see-also",level:2}];function d(e){let c={a:"a",code:"code",h1:"h1",h2:"h2",h3:"h3",header:"header",li:"li",p:"p",pre:"pre",ul:"ul",...(0,a.a)(),...e.components};return(0,o.jsxs)(o.Fragment,{children:[(0,o.jsx)(c.header,{children:(0,o.jsx)(c.h1,{id:"calicoctl-datastore-migrate-unlock",children:"calicoctl datastore migrate unlock"})}),"\n",(0,o.jsxs)(c.p,{children:["This sections describes the ",(0,o.jsx)(c.code,{children:"calicoctl datastore migrate lock"})," command."]}),"\n",(0,o.jsxs)(c.p,{children:["Read the ",(0,o.jsx)(c.a,{href:"/calico-enterprise/3.17/reference/clis/calicoctl/overview",children:"calicoctl Overview"}),"\nfor a full list of calicoctl commands."]}),"\n",(0,o.jsx)(c.h2,{id:"display-the-help-text-for-calicoctl-datastore-migrate-unlock-command",children:"Display the help text for 'calicoctl datastore migrate unlock' command"}),"\n",(0,o.jsxs)(c.p,{children:["Run ",(0,o.jsx)(c.code,{children:"calicoctl datastore migrate unlock --help"})," to display the following help menu for the\ncommand."]}),"\n",(0,o.jsx)(c.pre,{children:(0,o.jsx)(c.code,{children:"Usage:\n calicoctl datastore migrate unlock [--config=<CONFIG>]\n\nOptions:\n -h --help Show this screen.\n -c --config=<CONFIG> Path to the file containing connection\n configuration in YAML or JSON format.\n [default: /etc/calico/calicoctl.cfg]\n\nDescription:\n Unlock the datastore to complete migration. This once again allows\n Calico resources to take effect in the cluster.\n"})}),"\n",(0,o.jsx)(c.h3,{id:"examples",children:"Examples"}),"\n",(0,o.jsx)(c.p,{children:"Unlock the datastore after migration to allow the Calico resources to affect\nthe cluster."}),"\n",(0,o.jsx)(c.pre,{children:(0,o.jsx)(c.code,{className:"language-bash",children:"calicoctl datastore migrate unlock\n"})}),"\n",(0,o.jsx)(c.h3,{id:"general-options",children:"General options"}),"\n",(0,o.jsx)(c.pre,{children:(0,o.jsx)(c.code,{children:"-c --config=<CONFIG> Path to the file containing connection\n configuration in YAML or JSON format.\n [default: /etc/calico/calicoctl.cfg]\n"})}),"\n",(0,o.jsx)(c.h2,{id:"see-also",children:"See also"}),"\n",(0,o.jsxs)(c.ul,{children:["\n",(0,o.jsx)(c.li,{children:(0,o.jsx)(c.a,{href:"/calico-enterprise/3.17/operations/clis/calicoctl/install",children:"Install calicoctl"})}),"\n",(0,o.jsxs)(c.li,{children:[(0,o.jsx)(c.a,{href:"/calico-enterprise/3.17/reference/resources/overview",children:"Resources"})," for details on all valid resources, including file format\nand schema"]}),"\n"]})]})}function h(e={}){let{wrapper:c}={...(0,a.a)(),...e.components};return c?(0,o.jsx)(c,{...e,children:(0,o.jsx)(d,{...e})}):d(e)}},50065:function(e,c,t){t.d(c,{Z:function(){return l},a:function(){return i}});var n=t(67294);let o={},a=n.createContext(o);function i(e){let c=n.useContext(a);return n.useMemo(function(){return"function"==typeof e?e(c):{...c,...e}},[c,e])}function l(e){let c;return c=e.disableParentContext?"function"==typeof e.components?e.components(o):e.components||o:i(e.components),n.createElement(a.Provider,{value:c},e.children)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.