-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
1
-
False
-
-
False
-
subs-cost
https://focus.finops.org/focus-specification/v1-1/
https://learn.finops.org/introduction-to-focus
Use cases for Cost Management:
https://docs.google.com/presentation/d/1w_4iDFZB_Akv6in0R1vFWSxOLOKwZ5ELPB3Ow-dnom8/edit?usp=sharing
FOCUS is actually several things:
a) FOCUS ingest without authentication, much like the customer-filtered flows in the current AWS, Azure and GCP integrations. This could be as easy as "whenever Mr Customer creates a FOCUS integration, we will create a named endpoint where users can drop their files and we will process them"
b) FOCUS ingest with authentication, much like the current AWS, Azure and GCP integrations. This one will require some work to deal with Oracle Cloud, Tencent Cloud, Alibaba Cloud, etc authentication. IMHO this is low priority for now. The only one that might be interesting to (re)add is Oracle Cloud. If we have Oracle Cloud support through FOCUS, it becomes a low-maintenance feature (vs the previous support for Oracle Cloud, which required a lot of work by the Cost team to understand that specific format)
c) FOCUS export. This one probably requires the scheduler (to generate FOCUS format files every so often) and a named endpoint (where users can GET their files)
Named endpoints are not a must-have but they certainly look a lot better. The alternative is hitting some generic endpoint and passing the name as a parameter.
- relates to
-
COST-5916 RFE: Flat File API
-
- Backlog
-