CLOSED refer to https://github.com/infraql/infraql-original/issues/196

Feature Description Implement support to query nested or repeated fields in API responses, based upon the JSON parsing and utility functions available in MySQL

A basic subset of the available functions to be implemented include:

• JSON_LENGTH(<object or array field>[, path]) returns number of keys in an object or number of elements in an array
• JSON_KEYS(<object field>[, path]) returns a comma delimited list of keys, as ["key1", "key2", etc], this is a valid array object if returned to json output
• JSON_CONTAINS(<object or array field>, candidate[, path]) returns true or false if the object contains a value equal to the candidate, or an element equal to the candidate in an array
• JSON_EXTRACT(<object or array field>, path[, path] ...) returns the path or element specified from an array or object field
• JSON_PRETTY(json_val) expands pretty prints JSON in a cell (over multiple lines)

Feature Description Add support to give output columns aliases, this is supported by the Vitess parser but not implemented as yet

The following example illustrates the desired behaviour:

InfraQL* >>select id as fred from compute.networks where project = 'gcp-networking-intro';
|---------------------|
|         FRED        |
|---------------------|
| 1050180395817469648 |
|---------------------|
| 3584517666602292862 |
|---------------------|
| 5689506324057616817 |
|---------------------|

Aliases can be enclosed in single or double quotes, and can include embedded spaces (if embedded spaces are used, the alias must be enclosed with quotes)

Hello, I came across this project and was interested in trying it out as it claims to be provider agnostic, however all of the documentation uses Google Compute Platform as a provider, and I am not interested in using GCP at all, I want to be able to use InfraQL with smaller cloud providers like DigitalOcean or Linode.

So this an issue asking for documentation on how to use InfraQL with different providers, and how I as user can add more providers.

Feature Description Build a command line application in Golang called readplan, which takes one mandatory argument operation and one optional argument resource

Example(s) Valid combinations are: readplan show readplan select <resource_type> The show command reads the attached Terraform state file (terraform.tfstate), and returns a flattened json object with a list of all resources in the state file based upon the type value, for instance: [ “aws_s3_bucket_policy”, “aws_s3_bucket”, ... ]

Possible Approaches or Libraries to Consider The Select command, for a resource such as readplan select “aws_s3_bucket” Would return a flattened json response including the name and provider values for the resource as well as each key and its value from the instances list, for instance:

[
  {
    "name": "ext_stage",
    "provider": "provider.aws",
    "schema_version": 0,
    "attributes": {
      "acceleration_status": "",
      "acl": "private",
      "arn": "arn:aws:s3:::snowpipe-stage",
      "bucket": "snowpipe-stage",
      "bucket_domain_name": "snowpipe-stage.s3.amazonaws.com",

      "bucket_prefix": null,
      "bucket_regional_domain_name": "snowpipe-stage.s3.ap-southeast-2.amazonaws.com",

      "cors_rule": [],
      "force_destroy": false,
      "grant": [],
      "hosted_zone_id": "Z1WCIGYICN2BYD",
      "id": "snowpipe-stage",
      "lifecycle_rule": [],
      "logging": [],
      "object_lock_configuration": [],
      "policy": null,
      "region": "ap-southeast-2",
      "replication_configuration": [],
      "request_payer": "BucketOwner",

      "server_side_encryption_configuration": [
        {
          "rule": [
            {
              "apply_server_side_encryption_by_default": [
                {
                  "kms_master_key_id": "arn:aws:kms:ap-southeast-2:692401932224:alias/snowflake_stage",

                  "sse_algorithm": "aws:kms"
                }
              ]
            }
          ]
        }
      ],
      "tags": {
        "DateModified": "2020-03-15T21:20:53",
        "Origin": "Terraform",
        "Project": "Cloud Project"
      },
      "versioning": [
        {
          "enabled": false,
          "mfa_delete": false
        }
      ],
      "website": [],
      "website_domain": null,
      "website_endpoint": null
    },
    "private": "bnVsbA=="
  }
]

Additional context Attached is the terraform.tfstate file to read from. I had to rename it to .txt so as to be able to attach it to this issue. You can rename back to .tfstate on your local machine

terraform.tfstate.txt

Describe the bug

The SHOW RESOURCES command cannot properly resolve services when --usenonpreferredapis is invoked. This is likely because of ambiguity in the name field.

This example snippet is illustrative...

InfraQL* >>show extended resources from google.compute;
Could not find Service: 'compute' from Provider: 'google'
InfraQL* >>show services like '%compute%';
|----------------|---------|--------------------|
|       ID       |  NAME   |       TITLE        |
|----------------|---------|--------------------|
| compute__alpha | compute | Compute Engine API |
|----------------|---------|--------------------|
| compute__beta  | compute | Compute Engine API |
|----------------|---------|--------------------|
| compute__v1    | compute | Compute Engine API |
|----------------|---------|--------------------||--------------------|--------------------------------|---------|-----------|
InfraQL* >>

...note that there are 3 services with name = 'compute' and despite the use of '--nonpreferredapisit seems intuitive that the algorithm would resolve thepreferred` option (column not show but FYI third row is preferred).

To Reproduce Steps to reproduce the behavior:

1. Open the shell with ./infraql --verbose shell --usenonpreferredapis
2. Run command show extended resources from google.compute;
3. Observe output

Expected behavior

The service which is preferred should be returned from show extended resources from google.{SERVICE_NAME};, regardless of multiplicity of {SERVICE_NAME}.

Screenshots

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

Feature Description Add the SET command to the IQL grammar

SET property value

properties can be either:

1. global flags for infraql (such as --keyfilepath); or
2. provider properties including:

• gcpproject (GCP project)
• gcpregion (GCP region)
• proxy/address (possibly make the proxy settings global flags)
• proxy/port
• proxy/username
• proxy/password

Feature Description Add SHOW COLUMNS or SHOW FIELDS IQL meta operation, to filter columns from a resource

The syntax would be

SHOW [EXTENDED] {COLUMNS | FIELDS}
    {FROM | IN} _resource_
    [{FROM | IN} _service_]
    [LIKE 'pattern' | WHERE expr]

SHOW COLUMNS IN resource without any filter is an alias for DESCRIBE resource

SHOW EXTENDED COLUMNS IN resource without any filter is an alias for DESCRIBE EXTENDED resource