-
Notifications
You must be signed in to change notification settings - Fork 2.2k
docs: Add announcement for new repository URLs #18798
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
Merged
Merged
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
3403a9d
docs: Add announcement for new repository URLs
3c9d7a1
chore: Update check-spelling words
4f2e83a
chore: Update install documentation on package manager pages
9b67ba9
Address PR feedback
7b6f756
Apply suggestions from code review
8a28fdd
update dates to match new plan
jszwedko e87ac68
spelling
jszwedko fddb3db
add redirect
jszwedko File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
124 changes: 124 additions & 0 deletions
124
website/content/en/highlights/2023-11-07-new-linux-repos.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,124 @@ | ||
| --- | ||
| date: "2023-11-07" | ||
| title: "A New Home for Linux Packages" | ||
| description: "" | ||
| authors: ["spencergilbert"] | ||
| pr_numbers: [] | ||
| release: "0.34.0" | ||
| hide_on_release_notes: false | ||
| badges: | ||
| type: "announcement" | ||
| --- | ||
|
|
||
| Starting with Vector's `0.34.0` release, the `deb` and `rpm` packages will have | ||
| a new home at `vector.dev` courtesy of Datadog. We'll continue to publish | ||
| packages to both the new and existing locations through the end of **2023**. | ||
|
|
||
| {{< warning >}} | ||
| Starting in **2024**, we will stop using `timber.io` and exclusively publish packages | ||
| to `vector.dev`. | ||
| {{< /warning >}} | ||
|
|
||
| We aim to make this a seamless transition by providing plenty of time for you to switch | ||
| repositories, as well as by publishing previous versions of Vector with the new | ||
| repository as a drop-in replacement, so you don't have to update your Vector version. | ||
|
|
||
| If you have any questions or concerns don't hesitate to reach out on [Discord] | ||
| or [Discussions]! | ||
|
|
||
| ## Migration guide | ||
|
|
||
| The following command **removes** the existing repository and configures the | ||
| new repository. | ||
|
|
||
| ```sh | ||
| CSM_MIGRATE=true bash -c "$(curl -L https://s3.amazonaws.com/dd-agent/scripts/install_script_vector0.sh)" | ||
| ``` | ||
|
|
||
| Alternatively, `CSM_MIGRATE` may be left unset to leave the removal of the | ||
| existing repository to your discretion. | ||
|
|
||
| ### Manual step-by-step instructions | ||
|
|
||
| <details> | ||
| <summary>APT</summary> | ||
| 1. Remove the existing repository: | ||
|
|
||
| ```sh | ||
| rm "/etc/apt/sources.list.d/timber-vector.list" | ||
| ``` | ||
|
|
||
| 2. Run the following commands to set up APT to download through HTTPS: | ||
|
|
||
| ```sh | ||
| sudo apt-get update | ||
| sudo apt-get install apt-transport-https curl gnupg | ||
| ``` | ||
|
|
||
| 3. Run the following commands to set up the Vector `deb` repo on your system | ||
| and create a Datadog archive keyring: | ||
|
|
||
| ```sh | ||
| echo "deb [signed-by=/usr/share/keyrings/datadog-archive-keyring.gpg] https://apt.vector.dev/ stable vector-0" | sudo tee "/etc/apt/sources.list.d/vector.list" | ||
| sudo touch /usr/share/keyrings/datadog-archive-keyring.gpg | ||
| sudo chmod a+r /usr/share/keyrings/datadog-archive-keyring.gpg | ||
| curl https://keys.datadoghq.com/DATADOG_APT_KEY_CURRENT.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch | ||
| curl https://keys.datadoghq.com/DATADOG_APT_KEY_F14F620E.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch | ||
| curl https://keys.datadoghq.com/DATADOG_APT_KEY_C0962C7D.public | sudo gpg --no-default-keyring --keyring /usr/share/keyrings/datadog-archive-keyring.gpg --import --batch | ||
| ``` | ||
|
|
||
| 4. Run the following commands to update your local `apt` repo and install Vector: | ||
|
|
||
| ```sh | ||
| sudo apt-get update | ||
| sudo apt-get install vector | ||
| ``` | ||
|
|
||
| </details> | ||
|
|
||
| <details> | ||
| <summary>RPM</summary> | ||
|
|
||
| 1. Remove the existing repository: | ||
|
|
||
| ```sh | ||
| rm "/etc/yum.repos.d/timber-vector.repo" | ||
| ``` | ||
|
|
||
| 2. Run the following commands to set up the Vector `rpm` repo on your system: | ||
|
|
||
| ```sh | ||
| cat <<EOF > /etc/yum.repos.d/vector.repo | ||
| [vector] | ||
| name = Vector | ||
| baseurl = https://yum.vector.dev/stable/vector-0/\$basearch/ | ||
| enabled=1 | ||
| gpgcheck=1 | ||
| repo_gpgcheck=1 | ||
| gpgkey=https://keys.datadoghq.com/DATADOG_RPM_KEY_CURRENT.public | ||
| https://keys.datadoghq.com/DATADOG_RPM_KEY_B01082D3.public | ||
| https://keys.datadoghq.com/DATADOG_RPM_KEY_FD4BF915.public | ||
| EOF | ||
| ``` | ||
|
|
||
| **Note:** If you are running RHEL 8.1 or CentOS 8.1, use `repo_gpgcheck=0` instead of `repo_gpgcheck=1` in the configuration above. | ||
|
|
||
| 3. Update your packages and install Vector: | ||
|
|
||
| ```sh | ||
| sudo yum makecache | ||
| sudo yum install vector | ||
| ``` | ||
|
|
||
| </details> | ||
|
|
||
| ### Notes | ||
|
|
||
| * While the existing packages were migrated without rebuilding them, the RPM | ||
| packages _were_ re-signed with a Datadog GPG key. This will cause checksums | ||
| to not match between equivalent packages from `vector.dev` and `timber.io`. | ||
| * Once packages are released only to `vector.dev`, APT packages will be signed | ||
| by a Datadog GPG key. This update will be announced in advance. | ||
|
|
||
| [Discord]: https://chat.vector.dev/ | ||
| [Discussions]: https://discussions.vector.dev/ | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When running this script for the RPM installation, it prompted me when running
yum install vectorto accept the new keys. Is that expected? I somewhat expected this script to trust the keys already.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is because the Vector packages don't (yet?) depend on the signing keys packages which makes it a "separate" install? I know the deb's specify this explicitly, but I don't see where the rpm's do - maybe it's automagic?
@bkabrda do you know off the top of your head?