Skip to content

HMS-10265: templatize deployment.yaml#1406

Merged
jlsherrill merged 1 commit intocontent-services:mainfrom
jlsherrill:10265
Mar 19, 2026
Merged

HMS-10265: templatize deployment.yaml#1406
jlsherrill merged 1 commit intocontent-services:mainfrom
jlsherrill:10265

Conversation

@jlsherrill
Copy link
Copy Markdown
Member

Summary

Templatizes the deployment.yaml using a single list of environment variables.

Testing steps

tests pass

@jlsherrill jlsherrill requested a review from a team as a code owner March 5, 2026 21:42
@xbhouse
Copy link
Copy Markdown
Contributor

xbhouse commented Mar 5, 2026

@jlsherrill jlsherrill force-pushed the 10265 branch 3 times, most recently from b31e519 to 3ff67a5 Compare March 9, 2026 18:00
@rverdile rverdile self-assigned this Mar 10, 2026
default: stage
- name: IMAGE
value: quay.io/redhat-services-prod/insights-management-tenant/insights-content-sources/content-sources-backend
- name: WEEKLY_CRON_JOB
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Do we still need to keep this whole list of parameters at the bottom of the template updated? Can we ignore the ones defined in env-variables?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

we do, i could move it to the env file, which might make sense, so then they are all in a single place. I thought about it, but wasn't sold either way.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

so i mean to say, if you think it makes sense to put them there, i'll do that

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I think I like the idea of them being in a single place, so we don't have to remember to update them in two places. Were there drawbacks to that? I could be missing something. I guess it probably makes the parsing it a little trickier when generating the deployment.yaml

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

nah, i think its fine, i'll update

Comment thread mk/deployment.mk Outdated
Comment thread mk/deployment.mk
Copy link
Copy Markdown
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.

looks good!

@jlsherrill jlsherrill merged commit 2374703 into content-services:main Mar 19, 2026
20 checks passed
@jlsherrill jlsherrill deleted the 10265 branch March 19, 2026 17:13
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