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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample configuration of route entry #92

Closed
StephenColby opened this issue Apr 26, 2019 · 1 comment
Closed

Sample configuration of route entry #92

StephenColby opened this issue Apr 26, 2019 · 1 comment
Assignees

Comments

@StephenColby
Copy link

Can a sample route entry playbook be provided? Also in the example should be multiple network objects to show proper syntax of that for networks and gateway (single object). I am working on building a playbook for it now but have run into a few issues. When I look at the required field for upsertStaticRouteEntry it requires 2 path parameters in addition to the data parameters.

Parameter Required Type Description
parentId True string  
objId True string

The parent ID makes some sense in terms of the StaticRouteEntryContainer exposed by the API (even though there is only one...assuming this is to easily accommodate multiple routing tables later?) however why would an objectid also be required for an upsert operation?

@119Vik
Copy link
Contributor

119Vik commented May 16, 2019

@StephenColby I've just add PR #94 with update static_route_entry sample playbook.
objId is not required in the playbook, it's a mistake in the docs which will be fixed soon.
To specify route object which should be updated during update please use filters section of the ftd_configuration module.

@119Vik 119Vik closed this as completed Jul 23, 2019
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