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
Commands that require an stack to connect with will try to connect with the
stack of the current profile by default. This behaviour can be overridden
by setting the usual environment variables provided by `elastic-package shellinit`.
With this change `elastic-package shellinit` is not necessary when working
with stacks managed by elastic-package. shellinit is still useful to export
the configuration for other commands or scripts.
The environment variables can also be used to work with stacks not managed
by elastic-package.
Copy file name to clipboardExpand all lines: cmd/stack.go
+16-1Lines changed: 16 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,21 @@ For details on how to connect the service with the Elastic stack, see the [servi
48
48
49
49
You can customize your stack using profile settings, see [Elastic Package profiles](https://github.com/elastic/elastic-package/blob/main/README.md#elastic-package-profiles-1) section. These settings can be also overriden with the --parameter flag. Settings configured this way are not persisted.`
50
50
51
+
conststackShellinitLongDescription=`Use this command to export to the current shell the configuration of the stack managed by elastic-package.
52
+
53
+
The output of this command is intended to be evaluated by the current shell. For example in bash: 'eval $(elastic-package stack shellinit)'.
54
+
55
+
Relevant environment variables are:
56
+
57
+
- ELASTIC_PACKAGE_ELASTICSEARCH_HOST
58
+
- ELASTIC_PACKAGE_ELASTICSEARCH_USERNAME
59
+
- ELASTIC_PACKAGE_ELASTICSEARCH_PASSWORD
60
+
- ELASTIC_PACKAGE_KIBANA_HOST
61
+
- ELASTIC_PACKAGE_CA_CERT
62
+
63
+
You can also provide these environment variables manually. In that case elastic-package commands will use these settings.
Copy file name to clipboardExpand all lines: docs/howto/asset_testing.md
-6Lines changed: 0 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,12 +36,6 @@ elastic-package stack up -d
36
36
37
37
For a complete listing of options available for this command, run `elastic-package stack up -h` or `elastic-package help stack up`.
38
38
39
-
Next, you must set environment variables needed for further `elastic-package` commands.
40
-
41
-
```
42
-
$(elastic-package stack shellinit)
43
-
```
44
-
45
39
Next, you must invoke the asset loading test runner. This corresponds to steps 3 through 5 as described in the [_Conceptual process_](#Conceptual-process) section.
46
40
47
41
Navigate to the package's root folder (or any sub-folder under it) and run the following command.
0 commit comments