-
Notifications
You must be signed in to change notification settings - Fork 3
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 capability to manage "Libraries" to the provider #66
Comments
Could you explain a bit more about what is preventing you from using those Tracking Plan types? I am able to use those on my end. Are you perhaps getting an error like this which is in the connection (Sources cannot be connected to non
|
One of Tracking Plan's type is {
"name": "Some Library",
"description": "Some Library Desc"
"type": "RULE_LIBRARY",
"syncFromLibraries": [],
"excludedRulesFromLibraries": []
} Questions:
|
Yes you can create libraries in the provider now, are you running into issues?
No, we do not support importing libraries at this point, but is on our future roadmap. |
Hi @deanhuynh - so just to confirm the current terraform tracking plan capabilities allow us to:
What we do not have the capability to do is connect/synchronize a library of events/attributes with a tracking plan - is this correct? Is there another way we should be using libraries or is this just a capability gap with the API/terraform provider? It seems that if we create one it is just orphaned and cannot be connected to anything. Just want to check I am not missing something here. Thanks |
Yes this is correct It is a missing functionality at this point. We will consider prioritizing this early next year. Thanks! |
@ranand - great - thanks for confirming and will work around this for now. Are we OK to keep this feature request open for the additional capability as it is something we are looking to utilise? |
Is your feature request related to a problem? Please describe.
We are currently setting up Segment in Terraform and would like to be able to utilise "Libraries" but currently can only use LIVE tracking plans not
PROPERTY_LIBRARY
orRULE_LIBRARY
which is supported by the Public API. This means we will end up with repeated groups of events or attributes which will have to be maintained within the code.Describe the solution you'd like
Ability to manage the resource type
segment_tracking_plan
with typesPROPERTY_LIBRARY
orRULE_LIBRARY
which can then be linked to the LIVE tracking plan's.Describe alternatives you've considered
Additional context
The
PROPERTY_LIBRARY
is probably more of a priority at this stage and theRULE_LIBRARY
likely something we would want in the future.Public API reference to types noted above: https://docs.segmentapis.com/tag/Tracking-Plans#operation/createTrackingPlan
The text was updated successfully, but these errors were encountered: