Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add --api-listener-... flags to resource server #14

Merged

Conversation

jhernand
Copy link
Collaborator

This patch adds the --api-listener-... flags to the resource server:

$ ./oran-o2ims start resource-server \
--api-listener-address=localhost:8002 \

This is intended for use in the reverse proxy configuration started with proxy.sh, as it requires different ports for different services.

Note that a side effect of this is that the default port is now 8000 instead of 8080.

Related: https://issues.redhat.com/browse/MGMT-16113

This patch adds the `--api-listener-...` flags to the resource server:

```
$ ./oran-o2ims start resource-server \
--api-listener-address=localhost:8002 \
```

This is intended for use in the reverse proxy configuration started with
`proxy.sh`, as it requires different ports for different services.

Note that a side effect of this is that the default port is now `8000`
instead of `8080`.

Related: https://issues.redhat.com/browse/MGMT-16113
Signed-off-by: Juan Hernandez <[email protected]>
@jhernand
Copy link
Collaborator Author

FYI: @danielerez

--log-field="pid=%p" \
--api-listener-address="127.0.0.1:8002" \
--cloud-id="123" \
--backend-url="${BACKEND_URL}" \
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not related to this PR, just wonder if we should support multiple backend URLs?
I.e. should we open a ticket for supporting something like RESOURCE_BACKEND_URL, in case the search api is routed using a different domain? Or is it an unlikely scenario...

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, you are right, we should support multiple backend URLs, one for each kind of backend. Please open that ticket.

@danielerez
Copy link
Collaborator

lgtm

@jhernand jhernand merged commit b72277e into openshift-kni:main Nov 14, 2023
4 checks passed
@jhernand jhernand deleted the add_resource_server_to_proxy_script branch November 14, 2023 17:25
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.

2 participants