-
Notifications
You must be signed in to change notification settings - Fork 81
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
Migrate from fleet-ci bucket to Ingest bucket #3240
Comments
@mrodm Looking at this it should be as easy as updating the vault value used to retrieved the gcs bucket name right? Bucket name is retrieved here: fleet-server/.buildkite/hooks/pre-command Line 65 in 5e8a1e9
And bucket is used here: fleet-server/.buildkite/scripts/common.sh Line 105 in 5e8a1e9
|
It's also used in fleet-server/.buildkite/scripts/common.sh Line 121 in 5e8a1e9
The problem of updating the value directly in that vault path is that it could not be tested if that works or not in advance, and other builds (of any branch or PR) could fail. It is needed to ensure that the current service account has the required permissions to upload/write files into the new bucket. The service account used here is retrieved from this vault path:
NOTE: Just realized that fleet-server/.buildkite/scripts/common.sh Lines 119 to 139 in 5e8a1e9
|
In our Buildkite pipelines we are still relying on the fleet-ci buckets for DRA stage.
We need to stop using this one and rather start pushing artifacts to the ingest specific pipelines.
This change should be then back ported to the following branches:
https://github.com/elastic/fleet-server/blob/5e8a1e9f9f3cf9d7b97e8c41a7c6611b414eca55/.buildkite/hooks/pre-command#L11C1-L11C27
The text was updated successfully, but these errors were encountered: