arangodb-managed / oasisctl Goto Github PK

Please publish oasisctl to standard repositories like homebrew, apt, dnf, etc.

Installing an un-signed binary via a zip file on MacOS is a bit of a pain and can't be automated or auto-updated. It's not quite as annoying on Linux, but could be better.

My local copy of the API key seems to randomly stop working for me (See the example below). In the example, all of sudden the Oasis command stops working properly. I have rebuild the environmental variable used for authentication to get it working again. That is what the extra commands are doing. After it is rebuilt, it works fine.

$ ./oasis list organizations
1:22PM FTL Failed to list organizations error="rpc error: code = Unauthenticated desc = "
$ # Extracts the key_id and key_secret into variables
$ export key_id=$(awk --field-searator=" " '{print $2}' tempfile | sed -n '2p')
$ export key_secret=$(awk --field-searator=" " '{print $2}' tempfile | sed -n '3p')
$ # Create a variable
$ export OASIS_TOKEN=$(./oasis login --key-id=$key_id --key-secret=$key_secret)
$ # Lists the API keys
$ ./oasis list apikeys
Id                   | User-Id                             | Organization-Id | Readonly | Created-At | Expires-At | Revoked-At
ossacmae1a92qyaoellt | google-oauth2|103158209851494066752 |                 | -        | 1 hour ago |            |
$ ./oasis list organizations
Id        | Name                 | Description                      | Url                     | Created-At
105424485 | ScriptOrgDB          | This ORG was created by a script | /Organization/105424485 | 1 hour ago
...

I've used comments in the allowlist file to help identify the purpose for different IP ranges in there.

Unfortunately when we use oasisctl to update the allowlist using add-cidr-range-strings argument, the CIDR ranges are sorted which means I lose the ordering I have specified for IP ranges, as well as losing the context for comments that were added.

I've identified the following line which appears to apply a sort on the CIDR ranges when they are updated. I'm proposing here that should not be done - as a user, I expect any CIDR ranges to be added at the end of my list and I do care about the order of the ranges and the associated comments.

https://github.com/arangodb-managed/oasisctl/blob/7d02214cd338cbfc2e2780c5bb724a8e3fe31b64/cmd/security/update_ipallowlist.go#LL122C9-L122C35

string accepted_terms_and_conditions_id = 12;

Hi, I'm assuming the CLI uses the gRPC API on the backend, which is why I'm getting the following issues.

2:51PM FTL Failed to create deployment error="rpc error: code = InvalidArgument desc = accepting on terms & conditions is required

I was wondering from the CLI how does one accept the terms and conditions?

Thanks

https://arangodb.atlassian.net/jira/software/projects/OAS/boards/9?selectedIssue=OAS-111

Missing finer controls (i.e. increasing agents, database, or coordinators) for creating deployments

Found a problem with the Following Command

./oasis create deployment --cacertificate-id wttnefqllmtap66jrwc1 --organization-id 95616625 --project-id 95616808 --region-id gcp-europe-west4 --name ScriptDeployment --version 3.4.7

** Error: FTL Failed to create deployment error="rpc error: code = InvalidArgument desc = coordinators value 3 is greater than the limit of 2"

** Notes:

• There is no way to list available versions
• There is no way to specify size or advanced features

https://arangodb.atlassian.net/jira/software/projects/OAS/boards/9?selectedIssue=OAS-110

There needs to be warnings, when deleting ORGs, Projects, and Deployments.

Can't display version information of deployment, this is needed to view information about the deployment

Any subcommand that utilizes "./oasis delete" needs a warning that this operation can't be undone and requires confirmation. People will accidently take out infrastructure that they didn't intend to, because they typed something like "./oasis delete organization." Then didn't know it would take out deployments, projects, etc. If necessary it should have an override for people that want to bypass the warning, and no what they are doing.

Oasis needs a config file (i.e. ~/.oasis/config), including the environmental variables option it already has. This will allow the user to configure application defaults that will automatically be picked up by the oasis app.

The output from some Oasis command is too large and non-parseable by a script. There's no way to output specific information from the Oasis command (such as: URL, IDs, etc.) in another format (i.e. csv, json, etc.). This feature is needed so you can programmatically extract information you need for a script.

https://arangodb.atlassian.net/jira/software/projects/OAS/boards/9?selectedIssue=OAS-109

Display deployment state/status/servers
- Can't see storage utilization

https://arangodb.atlassian.net/jira/software/projects/OAS/boards/9?selectedIssue=OAS-112

It would be great if you download CAfor install it from Oasis. Otherwise download it such a way that it can be installed by a script on a platform.

'oasis create organization invite --email [email protected] -o 83036868' is working however if I specify the name of the organization like '-o MyOrg' a PermissionDenied is returned.

https://arangodb.atlassian.net/jira/software/projects/OAS/boards/9?selectedIssue=OAS-108

Can't displaying the status of the servers (i.e. running, upgrading), this is a specific function for looking at the state of individual server in a deployment. This would be useful for troubleshooting from the tool.

https://arangodb.atlassian.net/jira/software/projects/OAS/boards/9?selectedIssue=OAS-113

• update organization
• add organization members
• delete organization members
• update project
• update role
• update group
• add group members
• delete group members
• add policy binding
• delete policy binding
• ListMyOrganizationInvites

type error, disregard.