From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] bitbake: backport fetch2/aws: forward env-vars used in gitlab-ci K8s
Date: Sat, 25 Nov 2023 16:19:38 +0800 [thread overview]
Message-ID: <3417bbce-a07d-4280-afa3-cd5d9f825b88@siemens.com> (raw)
In-Reply-To: <ZWCsb1bayCK4EqUJ@ilbers.de>
On 24.11.23 22:00, Baurzhan Ismagulov wrote:
> On 2023-11-24 16:52, Uladzimir Bely wrote:
>>> --- 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):
>>
>> It looks like a fork of bitbake-2.0.12 we currently use in Isar that we
>> usually tend to avoid. But, probably not at this time...
>
> If that is already upstream, I think it should be pretty straightforward to
> backport this till we get 2.6.1 or so.
>
As discussed with Felix already in person: The only issue would be if we
decided to update once more in the current stable series. Then there is
the risk that we forget about this patch and overwrite it because
upstream stable will not see it (it's a feature, not a fix). Or is 2.0.x
EOL anyway?
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2023-11-25 8:19 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 [this message]
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
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=3417bbce-a07d-4280-afa3-cd5d9f825b88@siemens.com \
--to=jan.kiszka@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