[Core feature] SECRET FOR BUCKET NAME

[brucearctor]

Motivation: Why do you think this is important?

To address: #2421 , #2420 , etc... It would be prudent to have a Bucket which name is not pubilcly viewable. Having a GH SECRET in the repo with the bucket name would be most ideal. Naturally, this means it is not obvious where/when there is an AWS Bucket [ whether or not permissions set accordingly, better to 'hide' things ].

Goal: What should the final outcome look like, ideally?

A GH SECRET which can be used for bucket name.

Describe alternatives you've considered

Not having a Secret/Variable.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[github-actions]

Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏

[github-actions]

Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏

[eapolinario]

We're taking the investments in testing in a different route (essentially running in private clusters).