Skip to content

Conversation

@jlsherrill
Copy link
Member

@jlsherrill jlsherrill commented Jul 25, 2025

Summary

Creates some a method for generating the deployment.yaml file from a template and a yaml file with variables. Generally all variables are used for all items, except for the transform-pulp-logs which needs very specific special secrets.

Testing steps

Initially i'm looking for general feedback for the approach, not necessarily a full review at this time.

Largely created by cursor.

Copy link
Contributor

@rverdile rverdile left a comment

Choose a reason for hiding this comment

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

I haven't tested it, but I like the idea. I say let's do it.

valueFrom:
secretKeyRef:
name: content-sources-sentry
name: content-sources-glitchtip
Copy link
Member Author

Choose a reason for hiding this comment

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

apparently content-sources-sentry was removed a long time ago in favor of content-sources-glitchtip and a few of these were not updated

@xbhouse
Copy link
Contributor

xbhouse commented Jul 31, 2025

+1 to this idea!

i did a small test to generate the deployment with a new common env var and noticed that it wasn't added to the parameters section, that's something we'll probably want to add. maybe automate it if possible or a validation step to check that every env var has a matching parameter definition?

@rverdile
Copy link
Contributor

rverdile commented Dec 5, 2025

more evidence for the usefulness of this: #1326

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