# Integrations Development and \`elastic-package\` Question

**URL:** <https://discuss.elastic.co/t/integrations-development-and-elastic-package-question/330868>\
**Category:** Elastic Agent\
**Tags:** integrations\
**Created:** [April 26, 2023, 5:25pm UTC](https://discuss.elastic.co/t/integrations-development-and-elastic-package-question/330868 "2023-04-26T17:25:13Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MakoWish](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MakoWish](https://discuss.elastic.co/u/MakoWish)\
**Post date:** [April 26, 2023, 5:25pm UTC](https://discuss.elastic.co/t/integrations-development-and-elastic-package-question/330868/1 "2023-04-26T17:25:13Z")

</div>

I have been contributing a few PR's for enhancements and bug fixes to Integrations lately, and some of the bigger things I have been attempting require testing the package before submitting a PR. I have gotten my environment all set up, and I can successfully test an Integration package.

The issue I am running into, and hoping someone can help out with, is after I make more changes to the package. For instance, if I test the package once, then let's say I modified the ingest pipeline a bit. I do an `elastic-package clean`, `elastic-package build`, and then an `elastic-package install` in hopes those changes will be pushed to the test stack. Unfortunately, the ingest pipeline changes are not seen in the test cluster. Is there a way to completely remove the package from the test cluster without having to completely blow away the Docker containers and start from scratch? Either that, or force push the changes to the test cluster?

I would appreciate any help with this, as starting the test stack up after a `docker system prune -a` takes quite some time.

Thank you,  
Eric

---

<div class="post-metadata">

**Author:** ![kcreddy](https://avatars.discourse-cdn.com/v4/letter/k/6f9a4e/32.png) [@kcreddy](https://discuss.elastic.co/u/kcreddy)\
**Post date:** [April 27, 2023, 8:36am UTC](https://discuss.elastic.co/t/integrations-development-and-elastic-package-question/330868/2 "2023-04-27T08:36:38Z")

</div>

The command that usually works for me is:

```auto
elastic-package stack down && elastic-package build && elastic-package stack up -d -v

```

This should bring down the containers and bring them back up (usually takes about a minute). If for some reason your changes are not getting reflected, you could manually delete `build/` folder and run above command, but `elastic-package clean` should also do the same.

---

<div class="post-metadata">

**Author:** ![MakoWish](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MakoWish](https://discuss.elastic.co/u/MakoWish)\
**Post date:** [April 27, 2023, 2:59pm UTC](https://discuss.elastic.co/t/integrations-development-and-elastic-package-question/330868/3 "2023-04-27T14:59:42Z")

</div>

Thank you for the reply, Krishna! Okay, so the stack needs to be brought down, rebuild the package, then bring the stack back up. I just pushed my most recent PR I was working on, but I will create a test branch to give this a shot.

---

<div class="post-metadata">

**Author:** ![MakoWish](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MakoWish](https://discuss.elastic.co/u/MakoWish)\
**Post date:** [May 5, 2023, 2:38pm UTC](https://discuss.elastic.co/t/integrations-development-and-elastic-package-question/330868/4 "2023-05-05T14:38:08Z")

</div>

@kcreddy,

That does the trick. Thank you!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 2, 2023, 2:38pm UTC](https://discuss.elastic.co/t/integrations-development-and-elastic-package-question/330868/5 "2023-06-02T14:38:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.