Skip to content

Add documentation how to test packages with Serverless #2520

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.

Sign up for GitHub

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

Merged
merged 4 commits into from
Apr 8, 2025
Merged

Add documentation how to test packages with Serverless #2520

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
82e5df4
Add documentation how to test packages with Serverless
mrodm Apr 7, 2025
128c56a
Fix typo
mrodm Apr 7, 2025
83b637e
Update README
mrodm Apr 7, 2025
d9901e8
Update doc
mrodm Apr 7, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Fix typo
  • Loading branch information
@mrodm
mrodm committed Apr 7, 2025
commit 128c56a4c515a8cc3c6814543a10fa8302eb480d
10 changes: 5 additions & 5 deletions docs/howto/use_serverless_stack.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,8 @@ After completing these steps, create a new Elastic Serverless project by running
elastic-package stack up -v -d --provider serverless
```

Once this command finishes succesfully, your environment will be ready to use
any `elastic-package` subcommand (`install`, `dump`, `test`, ...) targetting the Serverless project created with the above command.
Once this command finishes successfully, your environment will be ready to use
any `elastic-package` subcommand (`install`, `dump`, `test`, ...) targeting the Serverless project created with the above command.

To clean up everything, run:
```sh
Expand All @@ -45,7 +45,7 @@ elastic-package stack down -v

**Recommendation:** Ensure that Serverless projects are properly deleted upon completion of testing to avoid any unexpected charges.

Even if the Serverless projects are available via the manegement UI [Elastic Cloud Projects](https://cloud.elastic.co/projects), please
Even if the Serverless projects are available via the management UI [Elastic Cloud Projects](https://cloud.elastic.co/projects), please
delete those projects using the `stack down` command mentioned above. This ensures that everything is cleaned up locally, and `elastic-package`
can continue working as expected.

Expand All @@ -54,7 +54,7 @@ If you need to switch back to a local stack, remember to change to the previous
elastic-package profiles use default
```

### Considerationg about testing with the `serverless` provider
### Considerations about testing with the `serverless` provider

There are some known issues when running pipeline tests with the `serverless` provider.

Expand All @@ -72,4 +72,4 @@ the `environment` provider instead.
You can learn more about this in [this document](https://github.com/elastic/elastic-package/blob/main/docs/howto/use_existing_stack.md).

**IMPORTANT**: This provider modifies the Fleet configuration of the target stack.
Avoid using it in environments that you use for other purpouses, specially in production environments
Avoid using it in environments that you use for other purposes, specially in production environments