feat(guacamole-client): Add guacamole-client

[stavros-k]

Description

Fixes #103

Type of change

• Feature/App addition
• Bugfix
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor of current code

How Has This Been Tested?

Notes:

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests to this description that prove my fix is effective or that my feature works
• I increased versions for any altered app according to semantic versioning

[Ornias1993]

It looks quite decent for a draft wip thingy actually :)

[stavros-k]

Ok initContainer 3-temp-hack extracts the files from /opt/guacamole/postgresql from the container into /opt/guacamole/postgresql-hack and downloads the correct driver into the -hack
Then 4-temp-hack copies everything from -hack into a pvc mounted on /opt/guacamole/postgresql which the actual app will use...

I'm pretty sure there is a much simpler way that I cannot see right now :D

[stavros-k]

App should be functional by now.

Tomorrow will look into polishing GUI and adding extensions like TOTP etc

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Details of the secret

Secret	Commit	Filename	Detected At
Generic High Entropy Secret	aacb5cc	charts/incubator/guacamole-client/values.yaml	22:28 January 13th, 2022	View secret
Generic High Entropy Secret	1888a41	charts/incubator/guacamole-client/values.yaml	22:28 January 13th, 2022	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

GitGuardian is an automated secrets detection service.We help developers and security teams secure the modern software development process.

 

Our GitHub checks need improvements? Share your feedbacks

[Ornias1993]

@stavros-k I think the radius thing is starting to overcomplicate it a bit.
We barely have a working radius setup anyway.

[stavros-k]

@stavros-k I think the radius thing is starting to overcomplicate it a bit. We barely have a working radius setup anyway.

I'll add it for now, as I'm already on it, and it's easier to fix things up later than add all this bulk.
Good thing is that all modules will be hidden in UI under checkboxes, so it won't add much clutter.

[truecharts-admin]

This PR is locked to prevent necro-posting on closed PRs. Please create a issue or contact staff on discord if you want to further discuss this