Is your feature request related to a problem? Please describe.
In journeys app we'd like to allow migrating both internal and external data groups, since the required data is already present inside the ucs files. Internal ones are already supported by ACC, but the external ones are not, even though they do have AS3 support.
Currently trying to convert a ltm profile fix + ltm data-group external pair results in a broken reference - the converted profile will contain a "use": "externalDataGroup" entry, even though no such data-group gets added to the declaration.
While sys file data-group is not supported by AS3 (there's no way to include the file contents inside a declaration, i think), it would be possible to add an ltm data-group external object with a reference to a file that would need to be created manually on destination BIG-IP before deploying the declaration itself.
I don't really see any other alternatives right now other than just ignoring these fields, which probably wouldn't be surprising - I'm not sure if adding a field that is expected to be deployed manually beforehands like suggested above is a valid usecase for ACC.
Is your feature request related to a problem? Please describe.
In journeys app we'd like to allow migrating both internal and external data groups, since the required data is already present inside the ucs files. Internal ones are already supported by ACC, but the external ones are not, even though they do have AS3 support.
Currently trying to convert a
ltm profile fix
+ltm data-group external
pair results in a broken reference - the converted profile will contain a"use": "externalDataGroup"
entry, even though no such data-group gets added to the declaration.Sample input:
Output as of 1.14.0
Describe the solution you'd like
While
sys file data-group
is not supported by AS3 (there's no way to include the file contents inside a declaration, i think), it would be possible to add anltm data-group external
object with a reference to a file that would need to be created manually on destination BIG-IP before deploying the declaration itself.Describe alternatives you've considered
I don't really see any other alternatives right now other than just ignoring these fields, which probably wouldn't be surprising - I'm not sure if adding a field that is expected to be deployed manually beforehands like suggested above is a valid usecase for ACC.