Skip to content
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

[discuss] Elastic Package Scripts #479

Open
mtojek opened this issue Aug 11, 2021 · 3 comments
Open

[discuss] Elastic Package Scripts #479

mtojek opened this issue Aug 11, 2021 · 3 comments
Assignees
Labels

Comments

@mtojek
Copy link
Contributor

mtojek commented Aug 11, 2021

What do you think about refactoring elastic-package a bit to be also available as a public library, which can be used to implement scripts?

I see few use cases around massive package modification:

  1. Update fields in all packages, because some of them have been published in ECS repository.
  2. Bump up versions in packages ready for release (maybe also: mark of them as GA/beta?).
  3. Rename text properties in manifests (title, descriptions) for purposes of Elastic docs publishing.
  4. Update ECS version to next version.

Inspirational post: https://blog.arduino.cc/2020/07/06/the-three-pillars-of-the-arduino-cli

@masci @jsoriano

@P1llus
Copy link
Member

P1llus commented Nov 17, 2021

This would be really cool! +1

@jsoriano
Copy link
Member

I guess #769 is in the line of this proposal? :)

@mtojek
Copy link
Contributor Author

mtojek commented Apr 13, 2022

The idea behind scripts was about introducing a more flexible engine that particular commands. Scripts would be oriented rather on the general processing and manipulation of package content.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants