-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Updating package registry snapshot distribution version #89776
Updating package registry snapshot distribution version #89776
Conversation
@ycombinator looks like some test need to be updated, I can do it if you want. |
@nchaulet that would be great, if you don't mind. Thanks! |
@nchaulet I just invited you to be a collaborator on my |
…-reg-dist-version
Pinging @elastic/fleet (Team:Fleet) |
There is some work to do to fix the issue, I will create a separate PR for that. |
Thanks. If it makes sense for you to push commits to this PR directly, please feel free to do so. I sent you an invite to collaborate on my kibana fork. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Test failure looks relevant, @nchaulet?
|
Yes the error is relevant I missed a part during the install transform
|
body: transform.content, | ||
}); | ||
} catch (err) { | ||
// swallow the error if the transform already exists. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but I'd like to double-check with @kevinlog that this is safe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this looks okay with me - I will get @pzl to comment as well asap
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
putting the same version, yeah we should logically be able to assume (aside from local dev situations) that it contains the same content trying to be installed then. Looks good.
Generally, the transform is deleted before install, right? I wonder why that isn't happening here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The transform is deleted if the saved object contains the transform, if our saved object and the state of ES differ this could happen
await callCluster('transport.request', { | ||
method: 'POST', | ||
path: `/_transform/${transform.installationName}/_start`, | ||
// Ignore error if the transform is already started | ||
ignore: [409], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above, cc @kevinlog
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here, looks OK - will check with @pzl
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as long as we don't think we're swallowing other problems that might be in a 409, sure
@elasticmachine merge upstream |
Looks OK to me - it seems we'd keep moving and not error when a transform of the same version is already installed. This seems OK to me as we'd always increment the version on the Endpoint package if there were new mappings, components, etc. I'll get the final 👍 from @pzl |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only thing I would worry about is the ignore all 409's when starting
We might end up with a false confidence if other classes of errors come back with 409's. If we think a transform is running, and it is not.. then a lot of data will never populate.
That said, none of these changes are introducing anything worse, so it's 👍 , just want to point out that caution
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Thanks for this @ycombinator @nchaulet! We haven't updated the distribution in a while :) |
@jen-huang Going forward, the distribution should be updated more frequently. I've added a manual step to the package registry release process (see last step in https://github.com/elastic/package-registry/blob/master/README.md#release). |
This PR updates the version of the snapshot package registry that's used by Fleet tests.