docs: Add announcement for new repository URLs

[spencergilbert]

No description provided.

[netlify]

✅ Deploy Preview for vrl-playground canceled.

Name	Link
🔨 Latest commit	fddb3db
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/6539360828fea20008249ed1

[netlify]

✅ Deploy Preview for vector-project ready!

Name	Link
🔨 Latest commit	fddb3db
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/65393608e23a7600077c927f
😎 Deploy Preview	https://deploy-preview-18798--vector-project.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[datadog-vectordotdev]

Datadog Report

Branch report: spencergilbert/vector.dev-repositories
Commit report: 87432a8

✅ vector: 0 Failed, 0 New Flaky, 1987 Passed, 0 Skipped, 1m 17.83s Wall Time

[spencergilbert]

@bkabrda if you'd like to review anything here now that you're back.

[maycmlee]

Left some docs suggestions! Let me know if you have any questions or if I changed the meaning of anything.

[spencergilbert]

Thanks @maycmlee!

[jszwedko]

Great!

The docs looked good. I tested different flows for apt and rpm:

• Just using the new install script
• Using the old install script, followed by the new one without migration
• Using the old install script, followed by the new one with migration
• Using the manual instructions

One question I have is about the script naming. The current naming of install_script_vector0.sh makes it sound like it is actually going to install Vector, but it only sets up the repos. I'm wondering if a better name might be something like setup_repos_vector0.sh?

[jszwedko]

When running this script for the RPM installation, it prompted me when running yum install vector to accept the new keys. Is that expected? I somewhat expected this script to trust the keys already.

[spencergilbert]

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?

[spencergilbert]

One question I have is about the script naming. The current naming of install_script_vector0.sh makes it sound like it is actually going to install Vector, but it only sets up the repos. I'm wondering if a better name might be something like setup_repos_vector0.sh?

I did consider this, but ultimately felt keeping it consistent with the other scripts felt right, especially considering the possibility of replacing the existing "install" script with one generated from the DD template - reducing maintenance/drift.

Of course that was just theoretical, and if we'd rather be more accurate today and change it down the line (if we even go that way) we could rename it.

Alternatively, @bkabrda had mentioned you had spoken and mentioned wanting the script available under the vector.dev domain - and the current location isn't. We could bypass the user side naming and add a redirect from setup.vector.dev (or whatever) to the S3 URL, that way internally the script is consistent but the user doesn't see it.

[jszwedko]

One question I have is about the script naming. The current naming of install_script_vector0.sh makes it sound like it is actually going to install Vector, but it only sets up the repos. I'm wondering if a better name might be something like setup_repos_vector0.sh?

I did consider this, but ultimately felt keeping it consistent with the other scripts felt right, especially considering the possibility of replacing the existing "install" script with one generated from the DD template - reducing maintenance/drift.

Of course that was just theoretical, and if we'd rather be more accurate today and change it down the line (if we even go that way) we could rename it.

Ah, yeah, that is fair. I think the Datadog Agent install scripts go further and actually install the Agent though, right? It seems like we wouldn't be able to template this until we unify the behavior and have the script instal Vector as well. The current scripts

Alternatively, @bkabrda had mentioned you had spoken and mentioned wanting the script available under the vector.dev domain - and the current location isn't. We could bypass the user side naming and add a redirect from setup.vector.dev (or whatever) to the S3 URL, that way internally the script is consistent but the user doesn't see it.

Also true, we did discuss hosting it on the Vector domain. We could do that via a redirect right now. I like setup.vector.dev. Maybe we can just go that route and leave the S3 name the same?

[spencergilbert]

Ah, yeah, that is fair. I think the Datadog Agent install scripts go further and actually install the Agent though, right? It seems like we wouldn't be able to template this until we unify the behavior and have the script instal Vector as well. The current scripts

Sorry, unclear from my end - the DD (agent/opw) scripts do go further. As-is we could template it from just the repo setup snippets.

Also true, we did discuss hosting it on the Vector domain. We could do that via a redirect right now. I like setup.vector.dev. Maybe we can just go that route and leave the S3 name the same?

Yep, that was my suggestion as well - of course if they look at the redirect they'll see the name which may be confusing, but the bucket name may also be confusing as well 🤷.

[datadog-vectordotdev]

Datadog Report

Branch report: spencergilbert/vector.dev-repositories
Commit report: b99741b

✅ vector: 0 Failed, 0 New Flaky, 1997 Passed, 0 Skipped, 1m 21s Wall Time

[jszwedko]

I updated the dates to reflect the new plan and added a redirect for setup.vector.dev.