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
title: "Quickly set up a Porter environment with required plugins"
4
+
description: "How to install multiple plugins with Porter"
5
+
date: "2023-01-24"
6
+
authorname: "Yingrong Zhao"
7
+
author: "@vinozzz"
8
+
authorlink: "https://github.com/vinozzz"
9
+
authorimage: "https://github.com/vinozzz.png"
10
+
tags: ["best-practice", "plugins"]
11
+
summary: |
12
+
Setting up your Porter environment with your required plugins using the new `--file` flag with `porter plugins install` command.
13
+
---
14
+
15
+
### Breaking change
16
+
The recent porter v1.0.5 release introduced a new flag `--file` on `porter plugins install` command. Its intention is to allow users to install multiple plugins through a plugins definition file with a single porter command. However, it did not work as expected due to bad file format.
17
+
18
+
The fix that contains the correct schema has been published with a new v1.0.6 release. If you have an existing plugins file, please update it to work with v1.0.6+.
19
+
20
+
### Install multiple plugins with a single command
21
+
Now, you can install multiple plugins using a plugin definition yaml file like below:
22
+
```yaml
23
+
schemaType: Plugins
24
+
schemaVersion: 1.0.0
25
+
plugins:
26
+
azure:
27
+
version: v1.0.1
28
+
kubernetes:
29
+
version: v1.0.1
30
+
```
31
+
32
+
After creating the file, you can run the command:
33
+
```bash
34
+
porter plugins install -f <path-to-the-file>
35
+
```
36
+
37
+
The output from the command should look like this:
38
+
```
39
+
installed azure plugin v1.0.1 (e361abc)
40
+
installed kubernetes plugin v1.0.1 (f01c944)
41
+
```
42
+
43
+
Make sure to update your current plugins schema file to the [latest format](/reference/file-formats/#plugins)
44
+
Please [let us know][contact] how the change went (good or bad), and we are happy to help if you have questions, or you would like help with your migration.
| schemaType | false | The type of document. This isn't used by Porter but is included when Porter outputs the file, so that editors can determine the resource type. |
175
176
| schemaVersion | true | The version of the Plugins schema used in this file. |
176
-
| <pluginName>.version | false | The version of the plugin. |
177
-
| <pluginName>.feedURL | false | The url of an atom feed where the plugin can be downloaded.
178
-
| <pluginName>.url | false | The url from where the plugin can be downloaded. |
179
-
| <pluginName>.mirror | false | The mirror of official Porter assets. |
177
+
| plugins.<pluginName>.version | false | The version of the plugin. |
178
+
| plugins.<pluginName>.feedURL | false | The url of an atom feed where the plugin can be downloaded.
179
+
| plugins.<pluginName>.url | false | The url from where the plugin can be downloaded. |
180
+
| plugins.<pluginName>.mirror | false | The mirror of official Porter assets. |
0 commit comments