Our organization has hundreds of connections spread out over multiple locations. It would be useful to be able to have one master connection file with all the various connection types, but to also be able to create other connection files which refer to those master connections without being copies of them.
This would allow for one connection file to be organized by location, another to be organized by service type, another by connection type, etc., without having to update multiple entries if a connection's details changed.
We can already refer to named credentials stored in other connection files, and I'm imagining this working much the same way.
1 Comment
Stefan Koell
said
over 6 years ago
Thanks for the feedback. This is an interesting idea. I will put that on our todo list...
Y.M. Gleaton
Our organization has hundreds of connections spread out over multiple locations. It would be useful to be able to have one master connection file with all the various connection types, but to also be able to create other connection files which refer to those master connections without being copies of them.
This would allow for one connection file to be organized by location, another to be organized by service type, another by connection type, etc., without having to update multiple entries if a connection's details changed.
We can already refer to named credentials stored in other connection files, and I'm imagining this working much the same way.