You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
-86Lines changed: 0 additions & 86 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,92 +48,6 @@ When adding a new tool:
48
48
3. Add the tool to an appropriate toolset (or create a new toolset if needed).
49
49
4. Register the toolset in `pkg/toolsets/` if it's a new toolset.
50
50
51
-
### Configuration Standards for Red Hat-Maintained Components
52
-
53
-
To ensure consistency across Red Hat-maintained toolsets and cluster providers, follow these standards when implementing certificate authority (CA) configuration:
54
-
55
-
#### Certificate Authority (CA) Configuration Standard
56
-
57
-
**Standard Pattern:** Certificate authorities must be configured using **file paths**, not inline PEM content.
- Accept `certificate_authority` as a string field in your toolset config struct.
63
-
- In the toolset parser function, resolve relative paths using `config.ConfigDirPathFromContext(ctx)` to make them relative to the config file directory.
64
-
- Store the resolved absolute path in the config struct.
65
-
- Validate in the `Validate()` method that `certificate_authority` is a valid file path using `os.Stat()`.
66
-
67
-
Example:
68
-
```go
69
-
func (c *Config) Validate() error {
70
-
// ... other validations ...
71
-
72
-
// Validate that certificate_authority is a valid file
0 commit comments