Skip to content

Commit

Permalink
Bump releases to version v0.18.12 (#211)
Browse files Browse the repository at this point in the history 
* Bump releases to version v0.18.12

* Auto generate

---------

Co-authored-by: metal-stack <info@metal-stack.io>
  • Loading branch information
@metal-robot
metal-robot[bot] and metal-stack committed Sep 6, 2024
1 parent 4a52e63 commit 11e4b36
Show file tree
Hide file tree
Showing 3 changed files with 56 additions and 54 deletions.
2 changes: 1 addition & 1 deletion Makefile
View file
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
.DEFAULT_GOAL := build
RELEASE_VERSION := $(or ${RELEASE_VERSION},"v0.18.11")
RELEASE_VERSION := $(or ${RELEASE_VERSION},"v0.18.12")

ifeq ($(CI),true)
DOCKER_TTY_ARG=
Expand Down
59 changes: 30 additions & 29 deletions docs/src/external/metalctl/docs/metalctl_network_create.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,35 +9,36 @@ metalctl network create [flags]
## Options

```
--bulk-output when used with --file (bulk operation): prints results at the end as a list. default is printing results intermediately during the operation, which causes single entities to be printed in a row.
-d, --description string description of the network to create. [optional]
--destination-prefixes strings destination prefixes in this network.
-f, --file string filename of the create or update request in yaml format, or - for stdin.
Example:
$ metalctl network describe network-1 -o yaml > network.yaml
$ vi network.yaml
$ # either via stdin
$ cat network.yaml | metalctl network create -f -
$ # or via file
$ metalctl network create -f network.yaml
the file can also contain multiple documents and perform a bulk operation.
-h, --help help for create
--id string id of the network to create. [optional]
--labels strings add initial labels, must be in the form of key=value, use it like: --labels "key1=value1,key2=value2".
-n, --name string name of the network to create. [optional]
--nat set nat flag of network, if set to true, traffic from this network will be natted.
-p, --partition string partition where this network should exist.
--prefixes strings prefixes in this network.
--privatesuper set private super flag of network, if set to true, this network is used to start machines there.
--project string project of the network to create. [optional]
--skip-security-prompts skips security prompt for bulk operations
--timestamps when used with --file (bulk operation): prints timestamps in-between the operations
--underlay set underlay flag of network, if set to true, this is used to transport underlay network traffic
--vrf int vrf of this network
--vrfshared vrf shared allows multiple networks to share a vrf
--additional-announcable-cidrs strings list of cidrs which are added to the route maps per tenant private network, these are typically pod- and service cidrs, can only be set in a supernetwork
--bulk-output when used with --file (bulk operation): prints results at the end as a list. default is printing results intermediately during the operation, which causes single entities to be printed in a row.
-d, --description string description of the network to create. [optional]
--destination-prefixes strings destination prefixes in this network.
-f, --file string filename of the create or update request in yaml format, or - for stdin.
Example:
$ metalctl network describe network-1 -o yaml > network.yaml
$ vi network.yaml
$ # either via stdin
$ cat network.yaml | metalctl network create -f -
$ # or via file
$ metalctl network create -f network.yaml
the file can also contain multiple documents and perform a bulk operation.
-h, --help help for create
--id string id of the network to create. [optional]
--labels strings add initial labels, must be in the form of key=value, use it like: --labels "key1=value1,key2=value2".
-n, --name string name of the network to create. [optional]
--nat set nat flag of network, if set to true, traffic from this network will be natted.
-p, --partition string partition where this network should exist.
--prefixes strings prefixes in this network.
--privatesuper set private super flag of network, if set to true, this network is used to start machines there.
--project string project of the network to create. [optional]
--skip-security-prompts skips security prompt for bulk operations
--timestamps when used with --file (bulk operation): prints timestamps in-between the operations
--underlay set underlay flag of network, if set to true, this is used to transport underlay network traffic
--vrf int vrf of this network
--vrfshared vrf shared allows multiple networks to share a vrf
```

## Options inherited from parent commands
Expand Down
49 changes: 25 additions & 24 deletions docs/src/external/metalctl/docs/metalctl_network_update.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,30 +9,31 @@ metalctl network update [flags]
## Options

```
--add-destinationprefixes strings destination prefixes to be added to the network [optional]
--add-prefixes strings prefixes to be added to the network [optional]
--bulk-output when used with --file (bulk operation): prints results at the end as a list. default is printing results intermediately during the operation, which causes single entities to be printed in a row.
--description string the description of the network [optional]
-f, --file string filename of the create or update request in yaml format, or - for stdin.
Example:
$ metalctl network describe network-1 -o yaml > network.yaml
$ vi network.yaml
$ # either via stdin
$ cat network.yaml | metalctl network update -f -
$ # or via file
$ metalctl network update -f network.yaml
the file can also contain multiple documents and perform a bulk operation.
-h, --help help for update
--labels strings the labels of the network, must be in the form of key=value, use it like: --labels "key1=value1,key2=value2". [optional]
--name string the name of the network [optional]
--remove-destinationprefixes strings destination prefixes to be removed from the network [optional]
--remove-prefixes strings prefixes to be removed from the network [optional]
--shared marks a network as shared or not [optional]
--skip-security-prompts skips security prompt for bulk operations
--timestamps when used with --file (bulk operation): prints timestamps in-between the operations
--add-destinationprefixes strings destination prefixes to be added to the network [optional]
--add-prefixes strings prefixes to be added to the network [optional]
--additional-announcable-cidrs strings list of cidrs which are added to the route maps per tenant private network, these are typically pod- and service cidrs, can only be set in a supernetwork
--bulk-output when used with --file (bulk operation): prints results at the end as a list. default is printing results intermediately during the operation, which causes single entities to be printed in a row.
--description string the description of the network [optional]
-f, --file string filename of the create or update request in yaml format, or - for stdin.
Example:
$ metalctl network describe network-1 -o yaml > network.yaml
$ vi network.yaml
$ # either via stdin
$ cat network.yaml | metalctl network update -f -
$ # or via file
$ metalctl network update -f network.yaml
the file can also contain multiple documents and perform a bulk operation.
-h, --help help for update
--labels strings the labels of the network, must be in the form of key=value, use it like: --labels "key1=value1,key2=value2". [optional]
--name string the name of the network [optional]
--remove-destinationprefixes strings destination prefixes to be removed from the network [optional]
--remove-prefixes strings prefixes to be removed from the network [optional]
--shared marks a network as shared or not [optional]
--skip-security-prompts skips security prompt for bulk operations
--timestamps when used with --file (bulk operation): prints timestamps in-between the operations
```

## Options inherited from parent commands
Expand Down

0 comments on commit 11e4b36

Please sign in to comment.