This repository has been archived by the owner on Jan 27, 2023. It is now read-only.
Add promote script #110
Closed
Add promote script #110
Conversation
This file contains 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
Initial draft of the promote script to promote a package from one branch to an other.
💚 Build Succeeded
Expand to view the summary
Build stats
|
|
@mtojek I started to work on the "promote" script. It is not complete yet and I want to get the magic from your script in about using a Github API key. |
|
I understand that this PR will deprecate the existing tooling (update-package-storage)? |
|
@mtojek No, this script should only promote packages from one release to the next. We will still need the update-package-storage script but need to adjust it. |
This was referenced Jul 2, 2020
|
Closing this PR as probably not needed in this form. |
thomasneirynck
pushed a commit
to thomasneirynck/package-storage
that referenced
this pull request
Sep 28, 2021
In the future metricbeat / filebeat and the agent will only support inputs. With this inputs become a first class citizen in our stack. An input is basically an agent configuration + an ingest pipeline. At the moment the package content is focused on having a config for the Beat or agent and all pipelines in one place. This complicates 2 things: * Knowing which ingest pipeline belongs to a specific input * Building integrations with multiple inputs: https://github.com/elastic/integrations/pulls Having the concept could simplify things as the package builder must not try to prevent naming configs of ingest pipeline by introducing extra long names. Also it should simplify testing as often testing is focused on inputs. With this all assets related to an input are together. As part of this PR there is an example on how such an input structure could look like. This should not replace the old place of ingest pipelines. If a user wants to build a package with just a ingest pipeline but not an input, this should also be possible in the future. The changed structure is described in the ASSET.md file.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Initial draft of the promote script to promote a package from one branch to an other.
This script does not necessarly belong here but didn't find a better place. Only opening as draft for now.