## What this PR does Backport of #4612 to `release-1.6`, together with its follow-up #4789. All three commits are cherry-picked. Two of them needed their `ApplicationDetailPage.test.tsx` cases added by hand, because on this branch that file has none of the virtual machine tab tests they sit next to on main. FoundationDB keeps its connection string in a ConfigMap that tenants may read, and the console had no view for ConfigMaps. The application page gets a ConfigMaps tab for the ConfigMaps named in the application's resource map, with a copy button for each value. Each read uses an exact-name field selector, so no general ConfigMap access is needed. The FoundationDB chart now renders its resource map with monitoring disabled too, and tenant roles may read it. If the resource map stops being readable after a successful read, the tab goes away instead of keeping the old names. ### Validation - All 6 FoundationDB chart tests pass, and so do all 338 console tests in 52 files and the TypeScript check. - Tests cover finding the ConfigMaps through the resource map, reading only the named ones in the active namespace, copying a value, a failed copy, a denied read, malformed resource maps, and a resource map that answers 403 or 404 after a successful read. The four tests for the last case fail without the #4789 commit. ### Screenshots The tab is the same as in #4612, which has a screenshot of it. ### Downstream repositories Walked the trigger map against the diff. It changes a FoundationDB chart template and its test, and the console, with no values, schema, CRD or `hack/` file, and the console is vendored in this repository. No companion repository needs an update. - [x] No downstream repository is affected by this change - [ ] [cozystack/website](https://github.com/cozystack/website) - follow-up: - [ ] [cozystack/terraform-provider-cozystack](https://github.com/cozystack/terraform-provider-cozystack) - follow-up: - [ ] [cozystack/ansible-cozystack](https://github.com/cozystack/ansible-cozystack) - follow-up: - [ ] [cozystack/ccp](https://github.com/cozystack/ccp) - follow-up: - [ ] [cozystack/talm](https://github.com/cozystack/talm) - follow-up: - [ ] [cozystack/cozyhr](https://github.com/cozystack/cozyhr) - follow-up: - [ ] [cozystack/cozy-proxy](https://github.com/cozystack/cozy-proxy) - follow-up: - [ ] [cozystack/cozystack-telemetry-server](https://github.com/cozystack/cozystack-telemetry-server) - follow-up: - [ ] [cozystack/external-apps-example](https://github.com/cozystack/external-apps-example) - follow-up: - [ ] [cozystack/examples](https://github.com/cozystack/examples) - follow-up: - [ ] [cozystack/community](https://github.com/cozystack/community) - follow-up: ### Release note ```release-note fix(dashboard): backport FoundationDB connection ConfigMaps to release-1.6 ```
Cozystack
Cozystack is a free platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.
