1"use strict";(globalThis.webpackChunkstackql_io||=[]).push([[22157],{27016(e,r,t){t.r(r),t.d(r,{default:()=>c,metadata:()=>s});var s=t(89913),a=t(74848),n=t(28453);const o={authorsImageUrls:[void 0]};function i(e){const r={a:"a",blockquote:"blockquote",code:"code",p:"p",pre:"pre",strong:"strong",...(0,n.R)(),...e.components},{Head:t}=r;return t||function(e,r){throw new Error("Expected "+(r?"component":"object")+" `"+e+"` to be defined: you likely forgot to import, pass, or provide it.")}("Head",!0),(0,a.jsxs)(a.Fragment,{children:[(0,a.jsx)(t,{children:(0,a.jsx)("meta",{name:"author",content:"Jeffrey Aven"})}),"\n",(0,a.jsxs)(r.blockquote,{children:["\n",(0,a.jsx)(r.p,{children:"Multi cloud visibility, SecOps, FinOps, DevOps made easy"}),"\n"]}),"\n",(0,a.jsxs)(r.p,{children:["Today marks a significant epoch in the evolution of the InfraQL/StackQL project. The StackQL provider registry allows contributors to add support for different providers (major cloud, alt cloud and SaaS providers) using a no-code approach. Developers simply add extensions to the providers OpenAPI spec using configuration documents (currently supporting ",(0,a.jsx)(r.code,{children:"yaml"})," and ",(0,a.jsx)(r.code,{children:"json"})," \u2013 with future support for ",(0,a.jsx)(r.code,{children:"toml"})," and ",(0,a.jsx)(r.code,{children:"hcl"}),"). These extensions allow StackQL to map an ORM to provider services, resources, and methods."]}),"\n",(0,a.jsx)(r.p,{children:"For example, for a future AWS provider you could run discovery commands such as:"}),"\n",(0,a.jsx)(r.pre,{children:(0,a.jsx)(r.code,{className:"language-sql",children:"SHOW SERVICES IN aws;\n/* shows the available services in AWS */\nSHOW RESOURCES IN aws.ec2;\n/* shows the available resources in the AWS EC2 service */\nDESCRIBE aws.ec2.instances;\n/* show available attributes in the aws.ec2.instances resource schema */\nSHOW METHODS IN aws.ec2.instances;\n/* shows available lifecycle methods \u2013 such as start, stop, etc which can be involved using the EXEC command */\n"})}),"\n",(0,a.jsx)(r.p,{children:"Or create a new EC2 instance using:"}),"\n",(0,a.jsx)(r.pre,{children:(0,a.jsx)(r.code,{className:"language-sql",children:"INSERT INTO aws.ec2.instances SELECT \u2026;\n"})}),"\n",(0,a.jsx)(r.p,{children:"View and report on instances and their properties using:"}),"\n",(0,a.jsx)(r.pre,{children:(0,a.jsx)(r.code,{className:"language-sql",children:"SELECT col(s) FROM aws.ec2.instances WHERE \u2026;\n"})}),"\n",(0,a.jsx)(r.p,{children:"Or clean up resources using:"}),"\n",(0,a.jsx)(r.pre,{children:(0,a.jsx)(r.code,{className:"language-sql",children:"DELETE FROM aws.ec2.instances WHERE \u2026;\n"})}),"\n",(0,a.jsxs)(r.p,{children:["The StackQL beta version supporting the provider registry is available for ",(0,a.jsx)(r.a,{href:"https://storage.googleapis.com/stackql-public-releases/latest/stackql_darwin_multiarch.pkg",children:(0,a.jsx)(r.strong,{children:"Mac (arm and amd)"})})," and ",(0,a.jsx)(r.a,{href:"https://releases.stackql.io/stackql/latest/stackql_linux_amd64.zip",children:(0,a.jsx)(r.strong,{children:"Linux"})}),", with a Windows version coming in the next few weeks."]}),"\n",(0,a.jsxs)(r.p,{children:["Providers are currently available for Google and Okta, see ",(0,a.jsx)(r.a,{href:"https://github.com/stackql/stackql-provider-registry",children:(0,a.jsx)(r.strong,{children:"StackQL Provider Registry repo"})})," and ",(0,a.jsx)(r.a,{href:"https://github.com/stackql/stackql/blob/main/docs/registry_contribution.md",children:(0,a.jsx)(r.strong,{children:"Developer Guide"})}),". We are encouraging developers to contribute \u2013 we would be happy to assist, just raise an issue or a PR."]})]})}function c(e={}){const{wrapper:r}={...(0,n.R)(),...e.components};return r?(0,a.jsx)(r,{...e,children:(0,a.jsx)(i,{...e})}):i(e)}t.d(r,["assets",0,o,"contentTitle",0,void 0,"frontMatter",0,{slug:"introducing-the-stackql-provider-registry",title:"Introducing the StackQL Provider Registry",authors:["jeffreyaven"],image:"/img/blog/stackql-registry-featured-image.png",description:"The StackQL provider registry allows contributors to add support for different providers (major cloud, alt cloud and SaaS providers) using a no-code approach.",keywords:["stackql","stackql provider registry","multicloud","asset management","cloud security"],tags:["stackql","stackql provider registry","multicloud","asset management","cloud security"]},"toc",0,[]])},28453(e,r,t){t.d(r,{R:()=>o,x:()=>i});var s=t(96540);const a={},n=s.createContext(a);function o(e){const r=s.useContext(n);return s.useMemo(function(){return"function"==typeof e?e(r):{...r,...e}},[r,e])}function i(e){let r;return r=e.disableParentContext?"function"==typeof e.components?e.components(a):e.components||a:o(e.components),s.createElement(n.Provider,{value:r},e.children)}},89913(e){e.exports=JSON.parse('{"permalink":"/blog/introducing-the-stackql-provider-registry","editUrl":"https://github.com/stackql/stackql.io/edit/main/blog/2022-03-17-introducing-the-stackql-provider-registry.md","source":"@site/blog/2022-03-17-introducing-the-stackql-provider-registry.md","title":"Introducing the StackQL Provider Registry","description":"The StackQL provider registry allows contributors to add support for different providers (major cloud, alt cloud and SaaS providers) using a no-code approach.","date":"2022-03-17T00:00:00.000Z","tags":[{"inline":true,"label":"stackql","permalink":"/blog/tags/stackql"},{"inline":true,"label":"stackql provider registry","permalink":"/blog/tags/stackql-provider-registry"},{"inline":true,"label":"multicloud","permalink":"/blog/tags/multicloud"},{"inline":true,"label":"asset management","permalink":"/blog/tags/asset-management"},{"inline":true,"label":"cloud security","permalink":"/blog/tags/cloud-security"}],"readingTime":1.47,"hasTruncateMarker":false,"authors":[{"name":"Jeffrey Aven","title":"Technologist and Cloud Consultant","url":"https://www.linkedin.com/in/jeffreyaven/","key":"jeffreyaven","page":null}],"frontMatter":{"slug":"introducing-the-stackql-provider-registry","title":"Introducing the StackQL Provider Registry","authors":["jeffreyaven"],"image":"/img/blog/stackql-registry-featured-image.png","description":"The StackQL provider registry allows contributors to add support for different providers (major cloud, alt cloud and SaaS providers) using a no-code approach.","keywords":["stackql","stackql provider registry","multicloud","asset management","cloud security"],"tags":["stackql","stackql provider registry","multicloud","asset management","cloud security"]},"unlisted":false,"prevItem":{"title":"GitHub Provider for StackQL Released","permalink":"/blog/github-provider-for-stackql-released"},"nextItem":{"title":"Big Query Cost Analysis using StackQL","permalink":"/blog/big-query-cost-analysis-using-stackql"}}')}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.