Skip to content
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

chore(NA): setup config folder with env var on fpm os packages #67433

Conversation

mistic
Copy link
Member

@mistic mistic commented May 26, 2020

That pr setup the ENV var KIBANA_PATH_CONF in order to have it pointing to the correct location of the config path. That has been discussed on #62468 and it is required for that PR.

@jbudz could you help me making sure it works as we expected? From what I was able to test what I'm doing here would do what we want.

@mistic mistic added chore Team:Operations Team label for Operations Team v8.0.0 release_note:skip Skip the PR/issue when compiling release notes v7.9.0 v7.7.1 labels May 26, 2020
@mistic mistic requested a review from jbudz May 26, 2020 23:49
@mistic mistic requested review from a team as code owners May 26, 2020 23:49
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@mistic
Copy link
Member Author

mistic commented May 28, 2020

@elasticmachine merge upstream

Copy link
Member

@jbudz jbudz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mistic
Copy link
Member Author

mistic commented May 28, 2020

@elasticmachine merge upstream

@mistic
Copy link
Member Author

mistic commented May 28, 2020

@jbudz had you the chance to test that approach both for sysv and systemd?

@mistic
Copy link
Member Author

mistic commented May 28, 2020

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

Copy link
Member

@jbudz jbudz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

many hours later (sorry!) - yes. we can remove "-c /etc/config/kibana.yml" from /etc/system.d/system/kibana.service but otherwise LGTM.

@mistic
Copy link
Member Author

mistic commented May 30, 2020

Thanks @jbudz ! I'll do this in another PR

@mistic mistic merged commit d0aeadf into elastic:master May 30, 2020
@mistic mistic added v7.8.1 and removed v7.7.1 labels May 30, 2020
mistic added a commit to mistic/kibana that referenced this pull request May 30, 2020
@mistic
Copy link
Member Author

mistic commented May 30, 2020

7.x: 0b4b454
7.8: ef0b82d

mistic added a commit that referenced this pull request May 30, 2020
…th fpm (#67433) (#67812)

Co-authored-by: Elastic Machine <[email protected]>

Co-authored-by: Elastic Machine <[email protected]>
mistic added a commit that referenced this pull request May 30, 2020
…th fpm (#67433) (#67813)

Co-authored-by: Elastic Machine <[email protected]>

Co-authored-by: Elastic Machine <[email protected]>
jbudz added a commit to jbudz/kibana that referenced this pull request Jun 30, 2021
When `(KBN|KIBANA)_PATH_CONF` was introduced, we removed the fallback lookup to
`/etc/kibana/kibana.yml` in elastic#67433.  This environment variable was added
to `/etc/default/kibana` and made available, scoped to the Kibana service
for deb and rpm packages.  This environment setting, however, is not available
when running binaries directly and caused the regression noted in

This re-adds a fallback lookup to `/etc/kibana/kibana.yml` when
searching for a kibana.yml configuration.

Testing
1) Install a .deb or .rpm package
2) `sudo -u kibana /usr/share/bin/kibana --version`

Closes elastic#101249
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore release_note:skip Skip the PR/issue when compiling release notes Team:Operations Team label for Operations Team v7.8.1 v7.9.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants