Debian Repo showing Artifactory as Origin and Label

[ZuperSero]

Elasticsearch Version

all, debian

Installed Plugins

No response

Java Version

bundled

OS Version

Linux rk12 6.1.0-1025-rockchip #25-Ubuntu SMP Mon Aug 26 23:01:14 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

Problem Description

Looks like earlier today something must have gone wrong when updating your debian repository as the origin and label changed.

its a minor fix, but can cause issues for automatic jobs running into errors.

apt update ...
E: Repository 'https://artifacts.elastic.co/packages/8.x/apt stable InRelease' changed its 'Origin' value from 'elastic' to 'Artifactory'
E: Repository 'https://artifacts.elastic.co/packages/8.x/apt stable InRelease' changed its 'Label' value from '. stable' to 'Artifactory'

On further inspection it seemed it showed

curl https://artifacts.elastic.co/packages/8.x/apt/dists/stable/InRelease
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Origin: Artifactory
Label: Artifactory
Suite: stable
Codename: stable
Date: Thu, 23 Jan 2025 15:50:17 UTC
Acquire-By-Hash: yes
Components: main
Architectures: amd64 arm64 i386
...

When it earlier today showed

cat /var/lib/apt/lists/artifacts.elastic.co_packages_8.x_apt_dists_stable_InRelease
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Origin: elastic
Label: . stable
Suite: stable
Codename: stable
Date: Tue, 21 Jan 2025 13:46:32 UTC
Architectures: amd64 arm64 i386
Components: main
Description: Generated by aptly

Steps to Reproduce

On a debian based system that has an older version of the repo on it.

sudo apt update

Logs (if relevant)

No response

[chriscroome]

Is this a mistake or intentional? Should we say Y to this prompt?

apt update
E: Repository 'https://artifacts.elastic.co/packages/8.x/apt stable InRelease' changed its 'Origin' value from 'elastic' to 'Artifactory'
E: Repository 'https://artifacts.elastic.co/packages/8.x/apt stable InRelease' changed its 'Label' value from '. stable' to 'Artifactory'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] N
E: Failed to fetch https://artifacts.elastic.co/packages/8.x/apt/dists/stable/InRelease  
E: Some index files failed to download. They have been ignored, or old ones used instead.

[kmurphy-everbridge]

this is breaking automation. Please advise if this is going to be a long term change, a bug (as it seems) or something different.