Feat: Use env variables to load api keys and secrets

[maverox]

Why do we need this improvement?

Exposed keys are not good for security and integrity, hence it is necessary to have this change

How will this change help?

It will help by securing exposed Api keys and secrets

Screenshots

No response

How could it be implemented/designed?

Yes it can be implemented simply by using .env files and loading the environment variables

🚧 Breaking changes

Yes

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[sambhavgupta0705]

@maverox where when do have keys currently exposed?

[maverox]

Algolia keys, I dont know whether i shoulf tell the exact location here? Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Sambhav Gupta ***@***.***> Sent: Thursday, March 21, 2024 10:26:01 PM To: asyncapi/website ***@***.***> Cc: Uzair Khan ***@***.***>; Mention ***@***.***> Subject: Re: [asyncapi/website] Feat: Use env variables to load api keys and secrets (Issue #2802) @maverox<https://github.com/maverox> where when do have keys currently exposed? — Reply to this email directly, view it on GitHub<#2802 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHBB34EX44IOUGYIY72D3UTYZMGKDAVCNFSM6AAAAABFBR6LTGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJTGAYDENZVGE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[sambhavgupta0705]

You can DM me on slack

[sambhavgupta0705]

@maverox I talked to @akshatnema and we came to a conclusion that it is not creating any problem to us so we are not planning to removing it for now

[sambhavgupta0705]

closing this as not planned for now