You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋 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.
The text was updated successfully, but these errors were encountered:
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 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. 👍
👋 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 therelatedResources
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.
The text was updated successfully, but these errors were encountered: