Skip to content

Move mechanisms to override stack docker images to profiles #1257

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jsoriano opened this issue May 9, 2023 · 1 comment
Open

Move mechanisms to override stack docker images to profiles #1257

jsoriano opened this issue May 9, 2023 · 1 comment

Comments

@jsoriano
Copy link
Member

jsoriano commented May 9, 2023

There are currently two main ways to override docker images used by the compose provider of elastic-package stack:

  • Use the image_ref_overrides setting in the .elastic-package/config.yml file.
  • Use the *_IMAGE_REF_OVERRIDE environment variables.

Both mechanisms are undocumented, barely supported and tested, and are not local to profiles, while the rest of stack resources and settings are.

We should establish a single supported mechanism for this, that works more like a profile setting, as other settings we have been recently adding (see #1211). And we should document it.

@mrodm
Copy link
Contributor

mrodm commented Aug 30, 2023

Just add a note that a new doc page was added to document how to use custom images:
#1323

Doc link: https://github.com/elastic/elastic-package/blob/60ee15405bfc1f759b745deffc56b7c2d33bdebe/docs/howto/custom_images.md

Even that, totally agree with establishing a single supported mechanism for this 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants