- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Surfaces (0.25 sec)
-
architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md
To keep the Groovy DSL ergonomic, we generate methods as necessary from the non-Groovy equivalents. Doing this provides the following specific benefits: - **Reduce the API surface** - We no longer need to maintain two methods. - **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL.
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Sun Mar 10 20:38:06 GMT 2024 - 1.8K bytes - Viewed (0) -
architecture-standards/0003-avoid-introducing-Groovy-types-to-public-api.md
To keep the Groovy DSL ergonomic, we generate methods as necessary from the non-Groovy equivalents. Doing this provides the following specific benefits: - **Reduce the API surface** - We no longer need to maintain two methods. - **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL.
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Wed Jan 31 14:32:10 GMT 2024 - 1.8K bytes - Viewed (0) -
manifests/charts/UPDATING-CHARTS.md
a single `affinity` field that is passed through as-is to the Kubernetes resource. This provides maximum flexibility with minimal API surface overhead. ## Making changes ## Step 1. Make changes in charts and values.yaml in `manifests` directory Be sure to provide sufficient documentation and example usage in values.yaml.
Plain Text - Registered: Wed Apr 24 22:53:08 GMT 2024 - Last Modified: Thu Jul 27 18:28:55 GMT 2023 - 3.2K bytes - Viewed (0)