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
{{ message }}
This repository has been archived by the owner on Feb 5, 2022. It is now read-only.
I'm using these examples in a lab to automation export and import policies between my gateways and I noticed that actions always consider the dependencies of a policy in the final bundle install file.
is there a way to remove or not consider the dependencies in these proccess? (For example, certificates or other gateway environment dependencies).
Thanks
The text was updated successfully, but these errors were encountered:
lucasfmarconi
changed the title
Export and Build Full Bundle always exporting dependencies too
Export and Build Full Bundle always considering Gateway config dependencies
Mar 1, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello folks,
I'm using these examples in a lab to automation export and import policies between my gateways and I noticed that actions always consider the dependencies of a policy in the final bundle install file.
is there a way to remove or not consider the dependencies in these proccess? (For example, certificates or other gateway environment dependencies).
Thanks
The text was updated successfully, but these errors were encountered: