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
Refactor profiles to decouple them from stack resources (#1140)
Changes included here:
* New `elastic-package profile use` command to select profile to use.
* Configuration files are not rewritten on upgrade.
* Stack and test runner files are managed by their own providers.
* Stack and test runner files are only written when the services are
started, and only if they are different.
* Stack files are templates now. Same files are used for multiple
versions. Runtime configuration can be passed now as data to
templates instead of requiring environment variables.
* Support for multiple stack providers.
Copy file name to clipboardExpand all lines: README.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -287,6 +287,12 @@ _Context: global_
287
287
288
288
289
289
290
+
### `elastic-package profiles use`
291
+
292
+
_Context: global_
293
+
294
+
295
+
290
296
### `elastic-package promote`
291
297
292
298
_Context: global_
@@ -383,7 +389,7 @@ By default the latest released version of the stack is spun up but it is possibl
383
389
384
390
Be aware that a common issue while trying to boot up the stack is that your Docker environments settings are too low in terms of memory threshold.
385
391
386
-
To ęxpose local packages in the Package Registry, build them first and boot up the stack from inside of the Git repository containing the package (e.g. elastic/integrations). They will be copied to the development stack (~/.elastic-package/stack/development) and used to build a custom Docker image of the Package Registry.
392
+
To expose local packages in the Package Registry, build them first and boot up the stack from inside of the Git repository containing the package (e.g. elastic/integrations). They will be copied to the development stack (~/.elastic-package/stack/development) and used to build a custom Docker image of the Package Registry.
387
393
388
394
For details on how to connect the service with the Elastic stack, see the [service command](https://github.com/elastic/elastic-package/blob/main/README.md#elastic-package-service).
0 commit comments