From: Uladzimir Bely <ubely@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] bitbake: backport fetch2/aws: forward env-vars used in gitlab-ci K8s
Date: Wed, 29 Nov 2023 12:24:03 +0300 [thread overview]
Message-ID: <81ff1e6427370ff36be92c4c2aa8f26a5d1f61d3.camel@ilbers.de> (raw)
In-Reply-To: <20231124075037.655070-1-felix.moessbauer@siemens.com>
On Fri, 2023-11-24 at 15:50 +0800, 'Felix Moessbauer' via isar-users
wrote:
> The patch "fetch2/aws: forward env-vars used in gitlab-ci K8s" was
> accepted upstream as c534526e. We need to backport it here to have
> it already until the next bitbake LTS version is released:
>
> This patch adds the following variables to the allow-list, which are
> used in the "IAM roles for AWS when using the GitLab chart":
>
> - AWS_ROLE_ARN
> - AWS_WEB_IDENTITY_TOKEN_FILE
>
> These variables are set in the CI job environment and are needed to
> access the sstate cache artifacts in a connected S3 bucket.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> bitbake/lib/bb/fetch2/__init__.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/bitbake/lib/bb/fetch2/__init__.py
> b/bitbake/lib/bb/fetch2/__init__.py
> index a3140626..008adab9 100644
> --- a/bitbake/lib/bb/fetch2/__init__.py
> +++ b/bitbake/lib/bb/fetch2/__init__.py
> @@ -850,6 +850,8 @@ FETCH_EXPORT_VARS = ['HOME', 'PATH',
> 'AWS_PROFILE',
> 'AWS_ACCESS_KEY_ID',
> 'AWS_SECRET_ACCESS_KEY',
> + 'AWS_ROLE_ARN',
> + 'AWS_WEB_IDENTITY_TOKEN_FILE',
> 'AWS_DEFAULT_REGION']
>
> def get_fetcher_environment(d):
> --
> 2.39.2
>
Applied to next, thanks.
prev parent reply other threads:[~2023-11-29 9:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 7:50 Felix Moessbauer
2023-11-24 13:52 ` Uladzimir Bely
2023-11-24 14:00 ` Baurzhan Ismagulov
2023-11-25 8:19 ` Jan Kiszka
2023-11-29 10:11 ` Baurzhan Ismagulov
2023-11-30 2:48 ` MOESSBAUER, Felix
2023-11-30 8:45 ` Baurzhan Ismagulov
2023-11-29 9:24 ` Uladzimir Bely [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81ff1e6427370ff36be92c4c2aa8f26a5d1f61d3.camel@ilbers.de \
--to=ubely@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox