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 of the \u003ccode\u003eFirewall.Types.Direction\u003c/code\u003e enum within the Compute Engine v1 API is 3.6.0.\u003c/p\u003e\n"],["\u003cp\u003eThis enum specifies the direction of traffic for a firewall, which can be either \u003ccode\u003eINGRESS\u003c/code\u003e (incoming) or \u003ccode\u003eEGRESS\u003c/code\u003e (outgoing).\u003c/p\u003e\n"],["\u003cp\u003eThe documentation includes versions of the API dating back to version 1.0.0, offering a range of choices for developers.\u003c/p\u003e\n"],["\u003cp\u003eThere are 3 possible fields that can be used when using \u003ccode\u003eFirewall.Types.Direction\u003c/code\u003e enum: \u003ccode\u003eEgress\u003c/code\u003e, \u003ccode\u003eIngress\u003c/code\u003e, \u003ccode\u003eUndefinedDirection\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe default traffic direction for firewalls is \u003ccode\u003eINGRESS\u003c/code\u003e, and source tags cannot be specified for \u003ccode\u003eEGRESS\u003c/code\u003e traffic.\u003c/p\u003e\n"]]],[],null,[]]
