stk-legacy import stack
Description
The stk-legacy import stack command adds a Stack to your project.
How does it work?
When you run the command, both the Stack Templates and Plugins you have created are available to use in the stk-legacy create app, stk-legacy create env and stk-legacy apply plugin commands.
If you have imported a Stack from a private or internal repository, you need to re-authenticate Git for all Plugins in your Stack.
You can configure Git to store your password with the command below and make it automatic:
git config --global credential.helper store
For more information, see the Git documentation.
Parameters
Check the available options in the command:
| Parameter | Description |
|---|---|
STACK_URL | Tells you the URL of the Git repository of a Stack. |
Local and Remote Stack
The STK CLI differentiates the Stacks imported by the stk-legacy import stack command associated with a URL, so when listing these Stacks they will be displayed as Stacks of type remote. While Stacks created by the command stk-legacy create stack will be displayed as Stacks of type local.
So the STK CLI automatically imports local Stacks into the default Stacks directory. In this case, any changes made to the Stack directory are automatically updated, without the need to use the stk-legacy update stack command.
To check which Stacks are of type local and remote, run the command below:
stk-legacy list stack
Check out the example with a Local Stack highlighted:
Example
See an example below:
- Adds the published Plugins and Templates on the Stack for STK CLI use:
stk-legacy import stack [URL do git]
See an example below:
Read more
Was this page helpful?