Assigned
Status Update
No update yet.
Comments
ha...@google.com
en...@google.com
SFDC cases associated with this issue have been notified.
ha...@google.com
va...@google.com
ar...@google.com
Hello,
Thanks for the feature request!
This has been forwarded to the Cloud Composer Engineering Team so that they may evaluate it. Note that there are no ETA's or guarantees of implementation for feature requests. All communication regarding this feature request is to be done here.
mi...@google.com
@ha...@google.com @va...@google.com should this ticket be in the public tracker?
ha...@google.com
@mi...@google.com,
This is visible to public.
This is visible to public.
av...@ebay.com Restricted
Restricted
av...@ebay.com Restricted
Restricted
Description
If you think that this is not a valid product bug (e.g. if it's a consult rather than a bug report,
or should have been solved by the Support team with better playbooks or training),
once you have responded please close it as "Won't Fix (Intended behavior)"
to help Support improve processes and training.
As per go/buganizer/concepts/issues
Business Impact
Without access to the Cloud Functions, Airflow DAGs fail, stopping any report generation for all the supported Markets in Production.
Issue category
Feature Request
Request summary
There is no clear document that Composer 3 traffic isn't considered as internal, or if there are alternative options, such as using Cloud Load Balancing.
Reproduction Steps
N/A
Assignee expected to adhere to Cloud/TI response and resolution SLOs (go/gcp-triage).http://metabug/?form=gcp-create-cloud-composer-feature-request
This bug was created using Metabug: