feat: New --private-key-file flag when creating a resource instance

[janelletavares]

Description of change

There are security concerns and UX hiccups around providing the value of a key at the command line rather than the filepath. This adds the file path flag option, and eventually we will deprecate the key value flag.

Also made resource create examples more complete in terms of missing resource types.

Fixes #381

Type of change

• New feature
• Bug fix
• Refactor
• Documentation

How was this tested?

• Unit Tests
• Tested in staging
• Tested in minikube

Demo

Additional flag in docs:

Flags:
      --ca-cert string            trusted certificates for verifying resource
      --client-cert string        client certificate for authenticating to the resource
      --client-key string         client private key for authenticating to the resource
      --env string                environment (name or UUID) where resource will be created
  -h, --help                      help for create
  -m, --metadata string           resource metadata
      --password string           password
      --private-key-file string   Path to private key file
      --ssh-private-key string    SSH tunneling private key
      --ssh-url string            SSH tunneling address
      --ssl                       use SSL
      --token string              API Token
      --type string               resource type (required)
  -u, --url string                resource url
      --username string           username

Additional references

Documentation updated

[jayjayjpg]

This is great, thank you for the command update, as well as the upgrade to the meroxa resources create docs! ✨

[jayjayjpg]

That's neat and as you already said, super helpful with creating snowflake resources in particular!

[jayjayjpg]

Nice test coverage as always! ✨