💚 CLA has been signed

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

The reason that the config.yml files had to change name is because of this PR: https://github.com/elastic/package-spec/pull/101/files#diff-b53b009efa91873f46aeec782b4cc40f8d0c9675d2ffcc1f184adae44cd72192R6

That change to the spec requires that the test files config.yml files be in the form of test-blah-config.yml. Unfortunately this means that to bring in the unsigned_long we have to bring in that change too. I believe the functionality to support multiple config.yml files is being worked on here: #209 Until that PR is merged we won't be able to update the elastic-package tool with the most recent package-spec.

How do we feel about pushing through this test-test-config.yml change in the interim to unblock package-spec changes?

@mtojek @ycombinator

Each config is supposed to be for a different system test within a data stream. So maybe just call them test-default-config.yml instead of test-test-config.yml?

Each config is supposed to be for a different system test within a data stream. So maybe just call them test-default-config.yml instead of test-test-config.yml?

I think that @adriansr should introduce these changes first, down to Integrations. They're blocking right now.

@AaronLamb1 Please clean up the elastic/package-spec#103 first. I noticed that you pushed lots of dependencies which IMHO wasn't necessary. Please run go mod tidy against them.

@mtojek here's the PR to clean up go.mod: elastic/package-spec#104

I think that @adriansr pushed his changes, including elastic-package. @jonathan-buttner @AaronLamb1 Could you please double-check if this PR is still valid?

closing because Adrian's PR pulled in the new spec 👍