Skip to content

Conversation

@thefirstofthe300
Copy link
Contributor

@thefirstofthe300 thefirstofthe300 commented Feb 6, 2025

To help gain confidence that future refactors will not completely break the chart, we should add unit testing to catch problems before they're merged.

@thefirstofthe300 thefirstofthe300 force-pushed the PLATFORM-2196/unit-testing branch from 4b5855f to 2e4d3d4 Compare February 6, 2025 00:17
@thefirstofthe300 thefirstofthe300 force-pushed the PLATFORM-2196/unit-testing branch from 2e4d3d4 to dac2dc1 Compare February 6, 2025 00:20
@thefirstofthe300 thefirstofthe300 marked this pull request as ready for review February 6, 2025 01:13
@thefirstofthe300 thefirstofthe300 requested review from a team as code owners February 6, 2025 01:13
*/}}
{{- define "gremlin.validateValues" -}}
{{- $messages := list -}}
{{- $messages := append $messages (include "gremlin.validateValues.secret" .) -}}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we call this gremlin.validateValues.certificate instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it matters one way or the other? I'd lean towards secret just because it's mainly about validating the managed secret inputs.

Co-authored-by: Phil Gebhardt <phil@gremlin.com>
@thefirstofthe300 thefirstofthe300 merged commit 5802c94 into master Feb 13, 2025
1 check passed
@ZachNo ZachNo deleted the PLATFORM-2196/unit-testing branch June 9, 2025 22:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants