💚 Switch bitnami to bitnami legacy

[DarkIsDude]

No description provided.

[bert-e]

Hello darkisdude,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options

name	description	privileged	authored
/after_pull_request	Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval	Bypass the pull request author's approval	⭐
/bypass_build_status	Bypass the build and test status	⭐
/bypass_commit_size	Bypass the check on the size of the changeset TBA	⭐
/bypass_incompatible_branch	Bypass the check on the source branch prefix	⭐
/bypass_jira_check	Bypass the Jira issue check	⭐
/bypass_peer_approval	Bypass the pull request peers' approval	⭐
/bypass_leader_approval	Bypass the pull request leaders' approval	⭐
/approve	Instruct Bert-E that the author has approved the pull request.		✍️
/create_pull_requests	Allow the creation of integration pull requests.
/create_integration_branches	Allow the creation of integration branches.
/no_octopus	Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity	Change review acceptance criteria from one reviewer at least to all reviewers
/wait	Instruct Bert-E not to run until further notice.

Available commands

name	description	privileged
/help	Print Bert-E's manual in the pull request.
/status	Print Bert-E's current status in the pull request TBA
/clear	Remove all comments from Bert-E from the history TBA
/retry	Re-start a fresh build TBA
/build	Re-start a fresh build TBA
/force_reset	Delete integration branches & pull requests, and restart merge process from the beginning.
/reset	Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

[bert-e]

Incorrect fix version

The Fix Version/s in issue UTAPI-117 contains:

• None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

• 8.2.4

Please check the Fix Version/s of UTAPI-117, or the target
branch of this pull request.

[bert-e]

Waiting for approval

The following approvals are needed before I can proceed with the merge:

• the author

• 2 peers

[anurag4DSB]

Can we have the issue number in the commit message for proper tracking?
https://scality.atlassian.net/wiki/spaces/ENG/pages/2038005821/Code+Review+Standard?focusedCommentId=3405545637

[DarkIsDude]

Can we have the issue number in the commit message for proper tracking? https://scality.atlassian.net/wiki/spaces/ENG/pages/2038005821/Code+Review+Standard?focusedCommentId=3405545637

@anurag4DSB done 🙏

[anurag4DSB]

Can we have the issue number in the commit message for proper tracking? https://scality.atlassian.net/wiki/spaces/ENG/pages/2038005821/Code+Review+Standard?focusedCommentId=3405545637

@anurag4DSB done 🙏

Can we also remove the emoji from the commit mesaage so that that if the font is not installed it doesnt break the systems and tools.

[DarkIsDude]

Can we also remove the emoji from the commit mesaage so that that if the font is not installed it doesnt break the systems and tools.

@anurag4DSB Do we have an agreement on that ? Gitmoji is pretty standard and I started to use it as some others do https://github.com/scality/artesca/commit/9fb645584cc28b55537f53c9166b0b259e5f8973. I'll remove it but I would like to know for next PR / commit message.

[anurag4DSB]

Can we also remove the emoji from the commit mesaage so that that if the font is not installed it doesnt break the systems and tools.

@anurag4DSB Do we have an agreement on that ? Gitmoji is pretty standard and I started to use it as some others do scality/artesca@9fb6455. I'll remove it but I would like to know for next PR / commit message.

Thanks for raising this. While Gitmoji is common in some projects, it isn’t consistently supported across all systems and tools we use, and can lead to readability or compatibility issues. To keep commit history reliable and portable, let’s avoid emojis in commit messages.

[DarkIsDude]

Thanks for raising this. While Gitmoji is common in some projects, it isn’t consistently supported across all systems and tools we use, and can lead to readability or compatibility issues. To keep commit history reliable and portable, let’s avoid emojis in commit messages.

That's done. Can you be more precise, I would start a new confluence page to make sure we can support Gitmoji as I (and I'm not the only one) like it 🙏

[DarkIsDude]

/approve

[bert-e]

I have successfully merged the changeset of this pull request
into targetted development branches:

• ✔️ development/8.2

The following branches have NOT changed:

• development/6.4
• development/7.10
• development/7.4
• development/7.70
• development/8.1

Please check the status of the associated issue UTAPI-117.

Goodbye darkisdude.

The following options are set: approve