The auto-generated layout can be wrong in some cases.

Imported k8s resources yaml defenition:

Same result in Safari/Chrome/Firefox.

It would be nice to have a possibility to zoom it using the mouse wheel and pan workspace.

Description

Executing clojure -m figwheel.main -b dev -r fails.

What is the current behavior?

$ clojure -m figwheel.main -b dev -r
DEPRECATED: Libs must be qualified, change ulmus => ulmus/ulmus (deps.edn)
DEPRECATED: Libs must be qualified, change recurrent => recurrent/recurrent (deps.edn)
DEPRECATED: Libs must be qualified, change garden => garden/garden (deps.edn)
Cloning: https://github.com/containership/konstellate-components
Error building classpath. Unable to clone /Users/marian/.gitlibs/_repos/github.com/containership/konstellate-components
remote: Repository not found.
fatal: repository 'https://github.com/containership/konstellate-components/' not found

The Github organization https://github.com/containership does not seem to exist.

What is the expected behavior?

A clear and concise description of what you expected to happen.

Additional Context

Just cloned the repository and ran the command from master. HEAD is 4801813469b78691d2e8024bd74ebd38468d27f8.

Reproduction

See above

Evidence

n/a

Description

What is the current behavior?

Currently, if a user deletes their workspace the nodes remain in the work area and are not deleted.

What is the expected behavior?

Nodes should be cleaned up when the workspace is deleted.

Additional Context

This is happening if the user has multiple workspaces or a single workspace

Reproduction

1. Delete Workspace
2. Observe

Evidence

A button, menu item, whatever.
For instance, I click and create a Pod.
I should now be allowed to click on the Pod entity (circle node) and have a way to "Show Relationships Available" in a list view... even cooler would be to allow to then click on one in the list and create from there, just as I do with the + button.

Description

Why should this feature be added?

To make selecting resources properties & sub-properties a lot simpler. This will save users a lot of unnecessary clicks.

How would you like the feature to work?

We've discussed a tree-view that once you select a property it's children will appear below and also be selectable.

What alternatives have been considered?

None at the moment.

Additional Context

This needs mocks

Description

What is the current behavior?

There is currently no top padding, so the array inputs are butting into each other.

What is the expected behavior?

There should be an 8px top margin to match other inputs.

Reproduction

1. Open the editor
2. Add an array property
3. Click the + to add more
4. Observe

Evidence

If you have a Kubernetes yaml generator, you could run it through k2tf to support terraform files as well, see https://github.com/sl1pm4t/k2tf#k2tf---kubernetes-yaml-to-terraform-hcl-converter

The demo link isn't working, is this expected? Thanks.

Description

What is the current behavior?

The swagger spec doesn't seem to be working for cron job creation. I think it's the path for it is not standard

What is the expected behavior?

Pull in spec similarly to what we are doing for all other resources.

Additional Context

This is probably affecting any resources that don't match the standard path

Reproduction

1. Add a cron job resource
2. Click on it and edit it
3. Observe

Evidence

Description

What is the current behavior?

Currently, you can add to an array by +1, but to remove an array you have to remove the whole grouping.

What is the expected behavior?

Users should be able to remove by -1 as well.

Additional Context

This should function similarly to how we treat key/value pairs.

Reproduction

1. Add multiple arrays
2. Remove them

Evidence

n/a

Description

What is the current behavior?

A clear and concise description of what is happening.
Following docs to deploy on macos with clojure.

What is the expected behavior?

A clear and concise description of what you expected to happen.

Additional Context

Add any other context about the problem.

Reproduction

1. Run the command '...'
   (⎈ |default:gitlab-managed-apps) 2:46:26 [cosmic:~/Devstack/zun] 7s 1 % clojure -m figwheel.main -b dev -r
   Execution error (FileNotFoundException) at clojure.main/main (main.java:40).
   Could not locate figwheel/main__init.class, figwheel/main.clj or figwheel/main.cljc on classpath.

Full report at:
/var/folders/nd/lnt1k7zj5mj3k6fr_kky6ll40000gn/T/clojure-4971199578006207098.edn
zsh: exit 1 clojure -m figwheel.main -b dev -r
2. ...

Evidence

If applicable, add logs or screenshots to help explain your problem.

Description

Why should this feature be added?

Currently, connections only work for a subset of resources, we need to ensure it works for every possible connection

How would you like the feature to work?

Similarly to how we handle connections now, but we need to allow the user to select how they want the resources to connect and extend it to enable more resources.

What alternatives have been considered?

none

Additional Context

Need mocks for this.

Now there is only "Save" button here.

There is a use case where a user can make changes, but don't want to save it.

For example, he made a mistake/typo and not sure that he wants to save it.

Handling Esc button would be useful too.

Description

Why should this feature be added?

This will give users clearer insight into what they can do from the beginning.

How would you like the feature to work?

A modal with the prompt:

"What would you like to do?"

a. Create Resource
b. Upload Resource

What alternatives have been considered?

Eventually, we would like to implement a more in-depth user onboarding process, however, I'm not certain that negates the usefulness of this feature.

Additional Context

Mock coming soon.