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
This is a plugin that helps to visualize the different components within a Spin application.
4
+
5
+
# Installation
6
+
7
+
## Install the latest version of the plugin
8
+
9
+
The latest stable release of the blueprint plugin can be installed like so:
10
+
11
+
```sh
12
+
spin plugins update
13
+
spin plugin install blueprint
14
+
```
15
+
16
+
## Install the canary version of the plugin
17
+
18
+
The canary release of the command trigger plugin represents the most recent commits on `main` and may not be stable, with some features still in progress.
Alternatively, use the `spin pluginify` plugin to install from a fresh build. This will use the pluginify manifest (`spin-pluginify.toml`) to package the plugin and proceed to install it:
27
+
28
+
```sh
29
+
spin plugins install pluginify
30
+
go build -o blueprint main.go
31
+
spin pluginify --install
32
+
```
33
+
34
+
# Usage
35
+
36
+
This plugin will read a `spin.toml` file within the same directory--or whatever path specified in the `--file` flag--and output tables detailing the Spin application as a whole, as well as individual components.
37
+
38
+
## See all available commands and flags:
39
+
40
+
```sh
41
+
spin blueprint --help
42
+
```
43
+
44
+
## Show all components
45
+
46
+
If in your terminal you are in the same directory as a spin.toml file:
47
+
48
+
```sh
49
+
spin blueprint show
50
+
```
51
+
52
+
If your spin.toml file is somewhere else:
53
+
54
+
```sh
55
+
56
+
spin blueprint show --file path/to/spin.toml
57
+
```
58
+
59
+
## Show a specific component
60
+
61
+
If in your terminal you are in the same directory as a spin.toml file:
62
+
63
+
```sh
64
+
spin blueprint show component-name
65
+
```
66
+
67
+
If your spin.toml file is somewhere else:
68
+
69
+
```sh
70
+
spin blueprint show --file path/to/spin.toml component-name
71
+
```
72
+
73
+
## Loading environment variables
74
+
75
+
You can pass environment variables directly:
76
+
77
+
```sh
78
+
SPIN_VARIABLE_FOO=bar spin blueprint show --file path/to/spin.toml
79
+
```
80
+
81
+
Or read a `.env` file:
82
+
83
+
```sh
84
+
spin blueprint --env path/to/file.env show component-name
0 commit comments