Merged
Conversation
9244b75 to
634e8e6
Compare
Contributor
Author
|
I would expect CI to fail on this PR as it stands. Specifically, I'd expect this test case to fail as the mock package for that test case has a I wonder why CI is passing on this test case 🤔 . I'm going to investigate this before I push a commit to fix the expected test failure in this PR. |
634e8e6 to
7b3e6f5
Compare
Contributor
Author
|
Okay, turns out I had accidentally pushed up the test fix commits already, which is why CI was passing earlier. I temporarily removed them now and CI is failing as expected. Phew! So just PEBCAK, nothing to see here 🙈 . I will push up the test fix commits again now. |
mtojek
approved these changes
Sep 18, 2020
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adjusts the spec for the
_dev/deployfolder as per this proposal: elastic/integrations#263 (comment).With this PR the spec will expect a specific folder name under
_dev/deploycorresponding to a supported deployment model. So a package could have this:or:
or:
For now, only the Docker-based deployment model is supported. The spec changes in this PR reflect this. In the future when we add other deployment models, we'll need to adjust the spec accordingly, e.g. to expect that there must be exactly one sub-folder under
_dev/deploysince a package should only specify one deployment model.