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

Locally built integration package not loaded into package-registry #914

Closed
drewdaemon opened this issue Jul 28, 2022 · 2 comments
Closed
Labels
bug Something isn't working Team:Ecosystem Label for the Packages Ecosystem team

Comments

@drewdaemon
Copy link
Contributor

I'm seeing this with version https://github.com/elastic/elastic-package/releases/tag/v0.58.1

1. Kubernetes package builds 1.22.0

elastic-package build
Build the package
...
Package built: /Users/andrewtate/workspace/integrations/build/packages/kubernetes-1.22.0.zip
Done

2. Stack runs and says it will load local packages

elastic-package stack up -v -d --services kibana
....
Custom build packages directory found: /Users/andrewtate/workspace/integrations/build/packages
Packages from the following directories will be loaded into the package-registry:
- built-in packages (package-storage:snapshot Docker image)
- /Users/andrewtate/workspace/integrations/build/packages
...
Creating network "elastic-package-stack_default" with the default driver
Creating elastic-package-stack_elasticsearch_1    ... done
Creating elastic-package-stack_package-registry_1 ... done
Creating elastic-package-stack_kibana_1           ... done
Creating elastic-package-stack_kibana_is_ready_1  ... done
Done

3. Package registry reports old kubernetes package version

https://127.0.0.1:8080/search
{
    "name": "kubernetes",
    "title": "Kubernetes",
    "version": "1.21.2",
    "release": "ga",
    "description": "Collect logs and metrics from Kubernetes clusters with Elastic Agent.",
    "type": "integration",
    "download": "/epr/kubernetes/kubernetes-1.21.2.zip",
    "path": "/package/kubernetes/1.21.2",
@MichaelKatsoulis
Copy link
Contributor

MichaelKatsoulis commented Jul 28, 2022

The command you run elastic-package stack up -v -d --services kibana does not re-build the registry. It just re-build kibana

@drewdaemon
Copy link
Contributor Author

It looks like both the k8s package versions were loaded into the package-registry, but I was seeing the older version because I was using an incompatible version of the Elastic stack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Team:Ecosystem Label for the Packages Ecosystem team
Projects
None yet
Development

No branches or pull requests

3 participants