Add new `stack.epr.base_url` profile setting by mrodm · Pull Request #3235 · elastic/elastic-package

mrodm · 2026-01-27T13:02:46Z

Follows #3232
Part of #2993
Fixes #2993

This PR is based on the changes in #3232 and includes a new profile setting stack.epr.base_url.

This new profile setting should be considered in those commands that require to run package-registry queries (e.g. elastic-package stack up or elastic-package status).

It is based on the elastic-package configuration (~/.elastic-package/config.yml):

Example:

stack:
    image_ref_overrides: {}
profile:
    current: default

## Optional
package_registry:
  base_url: "https://epr.elastic.co"
status:
  kibana_repository:
    base_url: "https://raw.githubusercontent.com/elastic/kibana"

This PR keeps the same default values:

Package Registry: https://epr.elastic.co
Kibana URL: https://raw.githubusercontent.com/elastic/kibana

In the case of the package registry, the value from the configuration file will be taken into consideration for the following commands such as:

elastic-package stack up (Serverless and Environment providers)
elastic-package stack update (Docker Compose provider)
elastic-package status
elastic-package test script (stackUp function)

This PR also takes into account:

the profile setting stack.epr.proxy_to. This configuration, if set, will take precedence to get the value to fill the value for the EPR_PROXY_TO environment variable in the packge-registry Dockerfile.
the profile setting stack.epr.base_url. This configuration, if set, will take precedence to get the URL used to query the Package Registry.

If those profile settings are not set, the one from the elastic-package configuration file will

Author's checklist

Test with custom package-registry and kibana URLs in elastic-package status.
Test with custom package-registry URLs in elastic-package stack (Serverless provider).
Test with custom package-registry URLs in elastic-package stack (Environment provider).
Ensure that elastic-package keeps using the default URLs if they are not specified in the config.
Test that configuration (~/.elastic-package/config.yml) is kept when changing the profiles (elastic-package profiles use`).
Update documentation

How to test this PR locally

Edit ~/.elastic-package/config.yml including:

package_registry:
  base_url: "https://epr-staging.elastic.co"
status:
  kibana_repository:
    base_url: "https://raw.githubusercontent.com/mrodm/kibana"

Test including the profile settings too:

stack.epr.proxy_to: "https://epr-staging.elastic.co"
stack.epr.base_url: "https://epr.elastic.co"

Run elastic-package status with different parameters:

# It should use the custom EPR URL
go run github.com/elastic/elastic-package -C test/packages/parallel/nginx status -vv

# It should use the custom EPR URL and the custom Kibana Repository URL
# Delete the cache folder to force query to the Github URL
rm -rf ~/.elastic-package/cache/kibana_config
go run github.com/elastic/elastic-package -C test/packages/parallel/nginx status -vv --info kibana.version,serverless.project_types
# Example output:
# TRACE Sending request to Package Registry API: https://epr-staging.elastic.co/search?all=false&experimental=true&package=nginx&prerelease=true
# TRACE Request Serverless Kibana configuration from https://raw.githubusercontent.com/mrodm/kibana/main/config/serverless.oblt.yml
# TRACE Request Serverless Kibana configuration from https://raw.githubusercontent.com/mrodm/kibana/main/config/serverless.security.yml
# TRACE Request Serverless Kibana configuration from https://raw.githubusercontent.com/mrodm/kibana/main/config/serverless.es.yml
# TRACE Sending request to Package Registry API: https://epr-staging.elastic.co/search?all=false&capabilities=apm&capabilities=observability&capabilities=uptime&experimental=true&package=nginx&prerelease=true
# TRACE Sending request to Package Registry API: https://epr-staging.elastic.co/search?all=false&capabilities=security&experimental=true&package=nginx&prerelease=true
# TRACE Sending request to Package Registry API: https://epr-staging.elastic.co/search?all=false&experimental=true&package=nginx&prerelease=true

Test for instance with environment provider:
- It requires to follow this example

# Once it is started Elasticsearch and Kibana following the previous doc

go run github.com/elastic/elastic-package profiles create environment
go run github.com/elastic/elastic-package profiles use environment

# this command show show that the new EPR URL is being used to get the fleet package
go run github.com/elastic/elastic-package stack up -vv -d --provider environment
# Example output:
# TRACE Sending request to Package Registry API: https://epr-staging.elastic.co/search?all=false&experimental=false&kibana.version=9.2.4&package=fleet_server&prerelease=false
# DEBUG Found fleet_server package - version 1.6.0


go run github.com/elastic/elastic-package stack down -v

…om-urls

mrodm · 2026-01-29T15:48:19Z

cmd/status.go

+	// Currently, this command does not use profile, so we take the URL from the application configuration
 	registryClient := registry.NewClient(appConfig.PackageRegistryBaseURL())


status command will just take into account the setting in the configuration file ~/.elastic-package/config.yml. Currently, it does not use any profile setting.

elasticmachine · 2026-01-29T15:52:06Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: c116b27

Failed CI Steps

:macos: :go: Integration test: build-zip

History

💚 Build #7084 succeeded 92f6906
💛 Build #7063 was flaky 2d21c02
💚 Build #7062 succeeded 83ee6ad

cc @mrodm

mrodm added 17 commits January 22, 2026 16:26

Add custom package-registry URL for status

f58a910

Add custom kibana URL for status

800cb9a

Use production URL from registry package

7f61f91

Rename functions

b141bae

Add documentation

62535cd

Add a status parent field for package-registry and kibana

a9ca9ee

Add tests

f5a03da

Add constant for kibana URL

2b04042

Update application configuration test

6408936

Merge remote-tracking branch 'upstream/main' into status-command-cust…

3ab5d98

…om-urls

Add support to use epr defined in elastic-package config in commands

6a1026c

Delete public var for Production EPR

0ce95c4

Update location for package_registry setting

38487e3

Update documentation

9035ba0

Rename method

c5e4bf2

Update documentation

7faea12

Add a new profile setting stack.epr.base_url

83ee6ad

mrodm self-assigned this Jan 27, 2026

mrodm added 2 commits January 27, 2026 14:55

Reorder imports

194dbca

Add comment

2d21c02

mrodm mentioned this pull request Jan 28, 2026

Allow to define EPR and Kibana repository URL in elastic-package configuration file #3232

Merged

5 tasks

Merge upstream/main into command-custom-epr-kibana-urls-profile

5806f45

mrodm marked this pull request as ready for review January 29, 2026 11:25

mrodm requested a review from a team January 29, 2026 11:25

mrodm added 2 commits January 29, 2026 15:59

Remove trace log message

92f6906

Merge upstream/main into command-custom-epr-kibana-urls-profile

c116b27

mrodm commented Jan 29, 2026

View reviewed changes

jsoriano approved these changes Jan 29, 2026

View reviewed changes

mrodm merged commit 6d87be2 into elastic:main Jan 30, 2026
3 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add new `stack.epr.base_url` profile setting#3235

Add new `stack.epr.base_url` profile setting#3235
mrodm merged 22 commits intoelastic:mainfrom
mrodm:command-custom-epr-kibana-urls-profile

mrodm commented Jan 27, 2026 •

edited

Loading

Uh oh!

mrodm Jan 29, 2026

Uh oh!

elasticmachine commented Jan 29, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

		// Currently, this command does not use profile, so we take the URL from the application configuration
		registryClient := registry.NewClient(appConfig.PackageRegistryBaseURL())

Conversation

mrodm commented Jan 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Author's checklist

How to test this PR locally

Uh oh!

mrodm Jan 29, 2026

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Jan 29, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

💛 Build succeeded, but was flaky

Failed CI Steps

History

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

mrodm commented Jan 27, 2026 •

edited

Loading

elasticmachine commented Jan 29, 2026 •

edited

Loading