I have not yet been able to reproduce this reliably, but it happened so often now, that I wanted to report it. After I use Commandeer for a while, pressing Reload (CMD-r) simply clears the window forever. Also Force Reload doesn't make anything reappear.

Opening a new window still works.

Commandeer version: 1.3.0
OS Version: MacOS 10.15.5 (19F101)

When using the Ansible runner, I need to add an environmental variable for my playbook.
When I click the gear icon, I am presented with the Ansible Settings window. When I click the "+ Add" button, beyond the animation- nothing occurs. Thus, I am unable to add the needed environmental variables.

Expected behavior: clicking the "+ Add" button should then allow me to add a key and a value.

The Localstack Install complains:

Docker : /bin/sh: docker: command not found
check Python : Python 2.7.10
close Pip : /bin/sh: pip: command not found
close LocalStack CLI : /bin/sh: localstack: command not found

Of these, only the last one is correct, the other two are in /usr/local/bin (installed through Homebrew)

I cannot find any option to set the PATH from inside Commandeer.

In both lambda invocation logs, and cloudwatch logs, it would be nice if the displayed text were selectable for clipboard copy, etc.

In the EC2 Regionscanner., there are orange Details buttons on every region, which do absolutely nothing when clicked...

Commandeer version: 0.6.0
Installed across multiple Linux Distro's via AppImage
Localstack version: 0.10.8 [started via localstack start command]
Further details: all testing has been done using awscli-local to interact with localstack

Issue: Although all resources created by Cloudformation within localstack appear without issue, Cloudformation itself never populates any data. Tested by creating several very simple Cloudformation stacks, ie creating S3 buckets, SQS queues etc..
Cloudformation within the Dashboard endlessly refreshes with no change

Expected: To see stack data, even if it's just the number of stacks currently deployed in localstack, within the Dashboards

As the tile says, when i press the Delete button to delete a bucket or a file from a bucket in a local S3 server it doesn't work or you have to press it multiple times before the file is actually deleted (i tried with the bucket but after pressing the delete button like 50 times the bucket was still there) :/

Steps to reproduce:

• Run localstack on your machine
• Open Commandeer and go to the S3 tab
• Make sure you are "connected" to your local account, wich is the localstack account
• Click on a bucket or on a file and hit the delete button on the right

Google discovered a couple of issues on mobile:

• Clickable elements too close together
• Content wider than screen

cc: @bwship

Handlers on Lambda functions can return a value either by directly returning something or by writing to an output stream. From the command line you can write this value to an output file, but in Commandeer, there is no indication that anything was returned.

The ask here is that there be a way to display values that are returned from an invoked Lambda.

It throws an error. v0.3.4

Setup a new MacBook Pro running 10.15.1. Downloaded Docker Desktop, ran a few test containers. Installed Commandeer 0.3.5. Commandeer can't detect Docker to setup LocalStack.

Can't scroll the menu on iOS.

On Mac, the keyboard shortcut CMD-a is commonly used for selecting all text in any textfield.

Commandeer uses it to create a new account, which is very confusing, as everytime I want to select text, a huge window pops up...

@fsproru Was there a major change on background events? I keep getting this error this morning when I try to start the app

Clicking on the tab moves it over and the next button doesn't work @bwship

Hi,
Could Commandeer make use of AWS cli config files and profiles?
~/.aws/credentials
~/.aws/config

It's usually the best practice for any soft leveraging aws sdks as any aws devs would use those already.

Furthermore the use of profiles is critical when using a unique AWS account (with credentials) to access ressources in different AWS accounts through IAM roles.

I am not sure if this one already has been reported but if I change the pagination per page count from 10 to 25 and open one record, closing window behaves a weird way. pagination count still shows 25 but list only shows first 10. Same thing also happens if I move through pages. i.e opening a record on page 5 then closing takes you back to page 1 but pagination still shows page 5.

Another issue arise after last update is refresh functionality. in any table if I click on refresh everything disappears. just blank page. then I go back to dynamodb dashboard, find table and reload.

Refresh Issue

Pagination issue

If you switched to a local account, it does not use the correct region.

When launching the App, it comes up in almost full screen every time, even though I made it smaller in the last session.

Messages added to queues are serialized twice.

A nice to have would be the ability to select a message body type,text ,json , etc because I find myself sending both stringified and raw payloads.

Hi there!

I just downloaded Commandeer and love it so far. Managing all of our AWS services with the AWS GUI has been a huge pain - I'm loving the transparency that Commandeer provides around which services we are using and how.

Our project is currently using localstack inside of a docker container to manage our local S3 and SQS dependencies. Commandeer was able to detect and provide visibility into the S3 bucket by default without issue, but for SQS it displays a "Network Failure" error message. The app works fine when looking at our AWS environment SQS queues.

Is there any way to get further insight into what might be causing the Network Failure with localstack? Thanks!

I'm running the latest Commandeer on Mac OS. When I boot up Localstack and generate resources from a CloudFormation template, I can hit refresh at the account level and in my AWS dashboard the resources are correctly there. But if I change my template to say remove 90% of the resources and redeploy my Localstack container and hit refresh in Commandeer all the old resources (DDB tables, s3 buckets, etc) that I removed from the CloudFormation template are still there.. They also persist between restarts of Commandeer making development against Localstack mostly unusable. The only way I can find to get around this is to go into my ~/Library/ApplicationSupport and remove the whole Commandeer directory which forces me to setup accounts all over, rewire the ports to use the EDGE_PORT to 4566 in all the AWS resource configurations at the AWS level (shouldn't this be the default for local BTW?).

Hi,

I've just downloded version for MacOs (ver 0.3.5) added Profile info (Firstname, Lastname and email) but when I try to "+ Add Account" nothing pops-up.

I've tried from several places, top bar, dashboard, from "window top bar" Cmd + A, nothing.

Do you know maybe what I'm doing wrong?

By the way, my MacOS is Catalina 10.15.1.

Hello,

I have a localstack instance running in a docker container with USE_SSL=false and Commandeer seems to detect my S3 and SQS successfully.

However, when I start localstack with USE_SSL=true Commandeer shows Network Failure on all the services mentioned before.

Kind regards,
Jose

The blog has formatting issues.

Clicking the Dock icon should activate the app, but it create a new window every time.

In the list of instances, the Name of the instance shows the name of the Key Pair, and not the name of the instance.

From the json, is currently shows the value of "KeyName", but it should be the value of the "Tags: key=Name" section.

I don't think this is the right place to mention this, but I wasn't sure where else to do so. None of the blog posts on the Commandeer website have dates on them, making it difficult to determine if the information is potentially out of date (amongst other things).

Are a lot of the files supposed to be empty?

https://github.com/commandeer/open/blob/development/templates/commandeer/cli/serviceCodeGenerator.ts
https://github.com/commandeer/open/blob/development/templates/commandeer/tank-service/main.ts
https://github.com/commandeer/open/blob/development/templates/commandeer/tank-service/package.json

etc...

if you go to your data file folder in application support and update the settings.json file to

hasSeenOnboarding: true

Fix will be going out in the next release this week.

When a Lambda is invoked in LocalStack, there are console logs generated by LocalStack to confirm that it was invoked and provide any warnings that are necesary. These logs do not appear if I invoke the Lambda via the Commandeer interface. To get these logs, I have to run my Lambda from the command line and then come back to Commandeer and see them. Typically, these logs look something like this:

2020-12-08T16:29:57:INFO:localstack.services.awslambda.lambda_executors: Running lambda cmd: CONTAINER_ID="$(docker create -i   -e DOCKER_LAMBDA_USE_STDIN="$DOCKER_LAMBDA_USE_STDIN" -e LOCALSTACK_HOSTNAME="$LOCALSTACK_HOSTNAME" -e EDGE_PORT="$EDGE_PORT" -e _HANDLER="$_HANDLER" -e AWS_LAMBDA_FUNCTION_TIMEOUT="$AWS_LAMBDA_FUNCTION_TIMEOUT" -e AWS_LAMBDA_FUNCTION_NAME="$AWS_LAMBDA_FUNCTION_NAME" -e AWS_LAMBDA_FUNCTION_VERSION="$AWS_LAMBDA_FUNCTION_VERSION" -e AWS_LAMBDA_FUNCTION_INVOKED_ARN="$AWS_LAMBDA_FUNCTION_INVOKED_ARN" -e AWS_LAMBDA_COGNITO_IDENTITY="$AWS_LAMBDA_COGNITO_IDENTITY"   --rm "lambci/lambda:java8" "com.example.localspringbootlocalstackpractice.Handler::handleRequest")";docker cp "/tmp/localstack/zipfile.2f7f19b3/." "$CONTAINER_ID:/var/task"; docker start -ai "$CONTAINER_ID";
2020-12-08T16:30:09:INFO:localstack.services.edge: Unable to find forwarding rule for host "e5681ebb97d7:4566", path "/", target header "", auth header "", data "b''"

The request is that all logs generated by LocalStack appear in the LocalStack terminal. If something is being done to repress these logs then I request that I be given the option of generating them

I am experiencing this issue with certain localstack services like api-gateway, sqs and sns.
I am using the commandeer version 1.4.1 on Ubuntu 20.04.1 LTS.

Using the AWS CLI i can see and create topics and queues for example.

I tried the solutions in the older issue but this is not resolving it:
#7

My docker file contains the following:

        container_name: "localstack"
        image: localstack/localstack-full
        networks:
            - workspace_app
        ports:
            - "4566-4599:4566-4599"
            - 9999:8080
        environment:
            - DEFAULT_REGION=eu-central-1
            - DEBUG=true
            - DOCKER_HOST=unix:///var/run/docker.sock
        volumes:
        - ./infra/localstack/data:/tmp/localstack
        - /var/run/docker.sock:/var/run/docker.sock

When there is partition key and sort key defined in a table Truncate operation fails

In the Navigation column, mouse-down on the text of an unselected entry, move the mouse over to the icon, and release.

This will select the entry, but not switch the corresponding view.

I only noticed, apparently I like to click in the area between icon and text, and then if you move the mouse just a little bit while clicking, this happens.

In documentation it mentions that table can be filtered quickly with indexed fields which seems to not work at all. Searching primary column or any indexed column value doesn't return any results. Also why id column is default in grid? I haven't understand this from 4-5 versions back. For instance as policy we are not allowed to use generic column names, each table should have identifier with it's name. userId, roleId etc. If commandeer can generate other columns from schema why there is also an id column in every table?

Cache the calls to AWS until the refresh button is hit.

Clicking on an entry with children:

• toggles the children on and off
• select the corresponding view (if it has one, some entries don't have one)
• but does NOT select the entry itself. The selection just stays wherever it was.

Eg. I'm in the "Whats New" entry, and click on "API Gateway".

It's also not a good idea to have the same click to the toggling AND the selecting.

It tries to open https://getcommandeer.com/docs but documentation is in docs.commandeer.com

Commandeer version: 0.6.0
Installed across multiple Linux Distro's via AppImage
Localstack version: 0.10.8 [started via localstack start command]
Further details: all testing has been done using awscli-local to interact with localstack

Issue: Only resources, ie S3 buckets, are populating within the Commandeer dashboard. When I add objects via the awslocal commands to interact with localstack, the files never show up within the dashboard

Expected: To see files and "folder" structures added from cli to the bucket within the Commandeer dashboard

It would be great to be able to assume roles within Commandeer when connecting to AWS accounts.

After deleting a record, popup that shows details gets stuck on screen. Cancel button doesn't function, Save button disabled.

I think this is also related to #89 and seems to happen after it fails truncating table.

Hi, I have reported this while back and it looks like it is resurrected. On dynamodb table data, changing pagination options or page doesn't reflect on table. For instance initially it loads 10 records of 20. I can see 10/20 at the bottom. if I change to second page, page number changes but data is still the same on the table.

If I reopen the same page then change 10 per page to 20/50 per page, table still shows only 10 records.

Is there a way to use the latest versions of the localstack (localstack/localstack-full:latest) image with commandeer.

I already have the docker image running however, when I start the commandeer localstack services, It launches (localstack/localstack:0.11.2)

Is there a way to configure to use the latest version.

When something goes wrong, and application restarted. All table names displays as last table had issue. Please see screenshot below

I have not been abled to set different ports to the defaults when using localstack infrastructure. Is there any way to do it?

There are 2 sqs queue : sms_queue (12 messages) and smsqueue (1 message)
On the dashboard total Messages count should be 13 instead of 121 .

Ok, this may be a minor detail. But the first time I played around with this, the "Install" button was gray, and the "Docker Container >" button next to it doesn't do anything.

Turns out I pressed the Play button. This complains that it cannot start LocalStack (obiously, as I don't have it installed), but it also disables the Install button, and never recovers from that situation.

Restarting Commandeer enables the button again.

Dragging the credentials.csv file makes it apper, but the button just stays grey. I had to enter the two Keys manually

getting this error /bin/sh: sls: command not found

Thank you for writing the much-needed serverless-dynamo-stream-plugin plugin.

fyi, with

configValidationMode: warn

serverless generates

Serverless: Configuration warning at 'functions['on-mutation'].events[0]': unsupported function event
Serverless:  
Serverless: Learn more about configuration validation here: http://slss.io/configuration-validation

on this version

$ .../node_modules/.bin/serverless --version
Building profileKey dev
Framework Core: 2.4.0 (local)
Plugin: 4.0.4
SDK: 2.3.2
Components: 3.2.1

for this yaml

service: conversation-message
configValidationMode: warn
frameworkVersion: '>=2.4.0'
custom:
  webpack:
    ...
package:
  individually: true
plugins:
  - serverless-webpack
  - serverless-plugin-git-variables
  - serverless-dynamo-stream-plugin
provider:
  ...
functions:
  on-mutation:
    handler: src/index.handler
    environment:
      mode: enabled
    events:
      - existingDynamoStream:
          tableName: ConversationMessage-rrx7agecrbelvawcvl7gvz2khm-dev
          streamType: NEW_AND_OLD_IMAGES
          startingPosition: LATEST
    name: conversation-message-dev-on-mutation