Repository navigation
Conversation
Python test results119 tests - 10 119 ✅ - 10 1m 8s ⏱️ +56s Results for commit d6e1c1d. ± Comparison against base commit 68abc19. This pull request removes 129 and adds 119 tests. Note that renamed tests count towards both. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
enroll a firewall without ports and let inspection label them
Kenny's PAN-OS inspection (#2564) finds a firewall's ports over LLDP and labels them outside/inside, so we shouldn't need to hand-write the ports JSON. But enroll-fw still required ports and made the node available straight away.
What does this change do?
enroll-fw now works two ways:
-p ports='[...]' -p physical_network=...): same as before. enroll-fw creates the ports, labels the two lowest interfaces outside/inside, and makes the node available.- enroll-fw creates the node
- keeps it out of the pool
- inspects it
- checks it now has an outside and an inside port
- then does it make the node available
- If a role is missing, the node stays manageable with an error, so a router can't take an unlabelled firewall.
also,
portsdefaults to[]andphysical_networkto""in the workflow.physical_networkis still required whenever ports are given.WIP : need to test in dev
Upgrade impact
upgrade-impactlabel and a release note: runscriv createfrom therepository root and describe the required action in the generated
changelog.d/file. See RELEASING.md.Operator action means anything a deployment has to do beyond a normal resync:
deploy repo or values changes, new or removed secrets, enabling or disabling a
component, or a manual one-time step.