Skip to content
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.

Issue #39: Make beats repo_key variable a unique name less likely to collide #40

Merged
merged 1 commit into from
Sep 11, 2019

Conversation

nyetwurk
Copy link
Contributor

No description provided.

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

@nyetwurk nyetwurk changed the title Issue 32: Make beats repo_key variable a unique name less likely to collide Issue #32: Make beats repo_key variable a unique name less likely to collide Sep 11, 2019
@nyetwurk nyetwurk changed the title Issue #32: Make beats repo_key variable a unique name less likely to collide Issue #39: Make beats repo_key variable a unique name less likely to collide Sep 11, 2019
@nyetwurk
Copy link
Contributor Author

#39

@jmlrt
Copy link
Member

jmlrt commented Sep 11, 2019

jenkins test this please

Copy link
Member

@jmlrt jmlrt left a comment

Choose a reason for hiding this comment

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

Looks good to me.
Thanks for this PR 👍

@jmlrt jmlrt merged commit ae737f4 into elastic:master Sep 11, 2019
@nyetwurk nyetwurk deleted the rename-repo-key-issue-39 branch July 29, 2020 06:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants