[
https://issues.apache.org/jira/browse/AIRAVATA-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066453#comment-18066453
]
Jayanth Vennamreddy commented on AIRAVATA-3961:
-----------------------------------------------
hey, I’d like to take this one. however, before I start, should this API live
in the Airavata API layer and what should be the source of truth for service
metadata?
> Add an API To Fetch Service Information from Gateway
> ----------------------------------------------------
>
> Key: AIRAVATA-3961
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3961
> Project: Airavata
> Issue Type: Improvement
> Components: Airavata API
> Reporter: Yasith Jayawardana
> Priority: Major
>
> Currently, users of Airavata APIs need to know the locations and settings for
> each service they wish to use. This is not ideal for Python SDK clients, as
> they need a (cumbersome) settings.ini file containing all service information
> upfront. Having an authentication-backed API to fetch the underlying service
> information from the gateway would allow the users to only need the gateway
> information upfront, with the rest of information inferred from the API
> response.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
