ldhertert / harness-cli Goto Github PK

Can't get read content for certain paths (i.e. harness config:get --path 'Setup/Cloud Providers/cv-demo.yaml')
https://harness.atlassian.net/browse/DX-2218

API Auth is not working for some parts of the API, such as fetching config as code tree for applications. (https://harness.atlassian.net/browse/DX-2211)

I'm intermittently getting timeout errors when saving infra defs

{
    "responseStatus": "FAILED",
    "errorMessage": "java.util.concurrent.TimeoutException",
    "filesStatus": null
}

https://harness.atlassian.net/browse/DX-2215

The published npm package is currently broken. Command files are not discovered for some reason. I believe that this may be due to some changes I made to the tsconfig file a little ways back.

• Documentation/examples for each step type #27
• Extract common logic to shared base (i.e. template rendering, file globbing, etc)
• Dry run support in each step
• Debug output in each step
• Option to dump workspace at each stage to disk
• Each step should have the option to push workspace changes to destination
• Show diff after each step
• Improve step factory logic
• Input validators
• Interactive mode
• Error handling

https://oclif.io/docs/commands

// custom usage string for help
  // this overrides the default usage
  static usage = 'mycommand --myflag'

  // examples to add to help
  // each can be multiline
  static examples = [
    '$ mycommand --force',
    '$ mycommand --help',
  ]

Hi All,

We are running harness on prem and wanted to check if harness cli will work with harness on prem.

I am getting 404 when trying to connect with harness cli.

need command to clone the service which would be really helpful

• Get certificate from URL
• Add cert to java keystore
• Add cert to OS certificate store

Most places that instantiate a new Harness API client are not currently passing the manager URL option, even though it is supported. Update all places where the client is created to support this option

core util, harness api, CLI, potentially templating.

https://harness.atlassian.net/browse/SWAT-3402

1. "secretManagerId" is a required field in CreateSecretInput. The expected behavior for me is that this should be an optional field, and if not present, the default secret manager should be used

2. To exacerbate the issue above, the secret manager API does not provide any way to filter/fetch the default secret manager, and there is no property available in the response that indicates whether or not a secret manager is default or not.

edit Additional findings after testing

3. When listing secret managers, “Harness Secret Manager” is not returned. In my account, I do not have any custom secret managers, so the response is an empty list

4. When retrieving a secret manager by name, and specifying “Harness Secret Manager”, I get an error that suggests that there is no secret manager with that name

5. I was able to retrieve the Harness Secret manager id by inspecting an existing secret via the API, but I get an error when trying to fetch this secret manager by id

The only time I’m able to successfully reference the default secret manager is when referencing it by ID in the createSecret mutation

https://harness.atlassian.net/browse/SWAT-3403

Harness API is throwing errors due to a serialization issue with CREATE_CUSTOM_DASHBOARDS and MANAGE_CUSTOM_DASHBOARDS permissions

Implement all instructions in https://github.com/wings-software/cv-demo as a template

https://github.com/jpillora/installer

https://github.com/fullstack-build/tslog

@kubernetes/client-node is by far the largest dependency in the project (24mb).

Try to move to https://github.com/godaddy/kubernetes-client

I have followed the documentation and with no success im getting a 401 error message i have tried to interact with the API using CURL and i have successfully been able to create a project using the same accountid & apikey so i verified its verified. please help with this if possible.

Hello 👋

I've started by installing the most recent 2 versions of the CLI on an Ubuntu LTS machine, and I'm getting some behaviour I don't understand! I'm running this in a POC account, with an API key scoped to an admin-level user.

To me, this /looks/ like the only available commands are help and autocomplete. I certainly can't get any other commands to invoke!

What am I getting wrong?

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.2 LTS
Release:        20.04
Codename:       focal
$ printenv HARNESS_ACCOUNT | awk '{print length($0)}'
22
$ printenv HARNESS_API_KEY | awk '{print length($0)}'
140
$ Harness-0.10.0 
VERSION
  @ldhertert/harness-cli/0.9.16 linux-x64 node-v12.18.1

USAGE
  $ harness [COMMAND]

COMMANDS
  autocomplete  display autocomplete installation instructions
  help          display help for harness

$ Harness-0.10.0 app:list
 ›   Error: command app:list not found
$ Harness-0.11.1 
VERSION
  @ldhertert/harness-cli/0.11.0 linux-x64 node-v12.18.1

USAGE
  $ harness [COMMAND]

COMMANDS
  autocomplete  display autocomplete installation instructions
  help          display help for harness

$ Harness-0.11.1 application:list
 ›   Error: command application:list not found
$ md5sum ~/bin/Harness-0.1*
cb8e47704865376b9225b08a9131f254  /home/ubuntu/bin/Harness-0.10.0
e79fdc2cebede9a31a7bbfd5aec64c36  /home/ubuntu/bin/Harness-0.11.1

The Harness GraphQL API does not currently support setting scopes on k8s cloud providers. For providers that inherit from delegate, this results in a cloud provider that is created without being scoped to any applications and needs to be manually updated.

For now, I'm using a workaround by hitting a private API to set the scopes to all apps/all envs.

I should be able to work around this using config as code API, however I'm currently getting an empty content when trying to pull the content.

Use drone cli locally to execute each step.

If running from a delegate, can automatically get accountId & manager url from config-delegate.yaml

Consider nixt - https://github.com/vesln/nixt

Instead of using throw/catch, use the patterns defined here across project.

I've put a hacky workaround in place, but need enhancements to add support in the GraphQL API