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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request : relationship query #305

Open
dstendardi opened this issue Nov 15, 2023 · 3 comments
Open

Feature request : relationship query #305

dstendardi opened this issue Nov 15, 2023 · 3 comments

Comments

@dstendardi
Copy link

dstendardi commented Nov 15, 2023

馃憢 Not sure this is the right place tot submit a feature request for the opslevel api, but here I go :

I am working on a contribution to the opslevel terraform provider so we can establish relationship between infrastructure and services via terraform. Unfortunately the Ops level api does not implement a query which allow to retrieve a single relationship by id. To work around this lack of feature, i had to specialise the resources (ie opslevel_infrastructure_relationship and use the relatedResources property. It works, but its quite suboptimal and make the code un-necessarily complicated, and thus leaves little chance for the contribution to be accepted in the current state.

Implementing a "relationship" query and making it available in the golang client would remove the need for such workaround.

@rocktavious
Copy link
Collaborator

Hey @dstendardi - I have passed this onto the team responsible for this API and they have put a ticket in their backlog for this. Unfortunately i do not have an ETA for when that might get done - your best bet is to talk to your opslevel support team so they can put added pressure to get the feature pushed up the backlog by product leadership.

If i hear the API is finished i'll report back here for you. Thank you for suggestion and willingness to work on a community integration for us. 馃帀

@dstendardi
Copy link
Author

Thank you very much @rocktavious . Should i keep this feature request open for tracking or close it ?

@rocktavious
Copy link
Collaborator

@dstendardi ya its ok to have it open here - we or you will need to eventually put the API functionality into opslevel-go once its in the GraphQL API. This can be the issue tracking that work. 馃憤

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

No branches or pull requests

2 participants