Reference documentation and code samples for the Compute Engine v1 API enum Firewall.Types.Direction.
Direction of traffic to which this firewall applies, either INGRESS or EGRESS. The default is INGRESS. For EGRESS traffic, you cannot specify the sourceTags fields.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-08 UTC."],[[["\u003cp\u003eThe latest version available for the \u003ccode\u003eFirewall.Types.Direction\u003c/code\u003e enum is 3.6.0, with documentation accessible via the provided link.\u003c/p\u003e\n"],["\u003cp\u003eThis page provides comprehensive documentation for the \u003ccode\u003eFirewall.Types.Direction\u003c/code\u003e enum, covering versions from 1.0.0 up to the latest 3.6.0.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eFirewall.Types.Direction\u003c/code\u003e enum, part of the Compute Engine v1 API, determines if a firewall rule applies to incoming (\u003ccode\u003eINGRESS\u003c/code\u003e) or outgoing (\u003ccode\u003eEGRESS\u003c/code\u003e) network traffic.\u003c/p\u003e\n"],["\u003cp\u003eThere are three fields within the enum: \u003ccode\u003eEgress\u003c/code\u003e (outgoing traffic), \u003ccode\u003eIngress\u003c/code\u003e (incoming traffic), and \u003ccode\u003eUndefinedDirection\u003c/code\u003e which is set if a value is not chosen.\u003c/p\u003e\n"],["\u003cp\u003eThe current version being viewed is version 2.17.0, which can be changed through the drop-down menu.\u003c/p\u003e\n"]]],[],null,[]]
