Add Templates feature to foreman-proxy - #519
Conversation
dcadf66 to
9a7993c
Compare
77b2cc9 to
6be7b5b
Compare
6be7b5b to
26ddc10
Compare
26ddc10 to
215ec14
Compare
215ec14 to
c5bb26e
Compare
|
Does templates need to be in the features.yaml? I do not see how the feature in this PR ensures foreman-proxy gets added. |
Yes, templates is declared in features.yaml under the foreman_proxy key (same pattern as bmc). I don't think we have a way to ensure if foreman-proxy gets added. |
713b3d9 to
ded1e9b
Compare
|
@ehelms Made some updates that ensures foreman-proxy gets added on the feature install. Not sure if that should be part of this PR. |
f0ba618 to
b20b505
Compare
|
Shouldn't the feature by added to It's currently the default in foreman-installer: https://github.com/theforeman/foreman-installer/blob/0448d5d129f8fe2ea514cfb7fe90857e0e3f15bd/config/foreman-proxy-content-answers.yaml#L30 |
|
@pablomh that's only for the content proxies, not for the normal install. It could be part of the proxy flavor. |
5485068 to
dcb008f
Compare
dcb008f to
748fe93
Compare
|
@shubhamsg199 What is the status here? |
88fc9f7 to
916293d
Compare
@jeremylenz Updated the PR, can you take a look? |
|
|
||
|
|
||
| @pytest.mark.feature('templates') | ||
| def test_templates_template_url(obsah_params, server_fqdn): |
There was a problem hiding this comment.
This tests is currently passing
There was a problem hiding this comment.
oh, because you changed it to read the params, not talk to the API to fetch the set value.
Signed-off-by: Shubham Ganar <shubhamsg123m@gmail.com>
Signed-off-by: Shubham Ganar <shubhamsg123m@gmail.com>
916293d to
7eb0af0
Compare
There was a problem hiding this comment.
🍏 LGTM 🍏
- Code looks clear
- All comments should be addressed.
- Tests are present
Tested with Packit, shortly:
Running foremanctl deploy --add-feature templates --templates-listen-on http --templates-url http://foremanctl9.vagrant.lan/ does not affect the *-pulp proxy.
Running foremanctl deploy --add-feature foreman-proxy will automatically enable templates on the newly running Foreman proxy service.
Merging as #675 is waiting for it.
| foreman_proxy_templates_listen_on: | ||
| parameter: --templates-listen-on | ||
| help: Templates proxy to listen on https, http, or both. | ||
| choices: | ||
| - http | ||
| - https | ||
| - both |
There was a problem hiding this comment.
Why is it needed to expose this? In the old installer we exposed it because it was the way we did, but it was an advanced option. In foremanctl I think shouldn't expose this.
| - both | ||
| foreman_proxy_templates_url: | ||
| parameter: --templates-url | ||
| help: URL that hosts will use to contact the proxy for provisioning templates (e.g. http://<proxy-fqdn>:8000). Required when templates feature is enabled. |
There was a problem hiding this comment.
There is a default which implies it isn't required to specify.
Why are you introducing these changes? (Problem description, related links)
What are the changes introduced in this pull request?
How to test this pull request
Steps to reproduce:
Checklist