* Support single endpoint deletion from multi-endpoints component
* Support single command deletion from multi-commands component
* Support single key-value item deletion from multi-key-value component
* Support single text item deletion from multi-text component
* Support single volume mount item deletion from multi-volume-mounts component
* Add Cypress test cases
* Git-ignore Cypress screenshots folder
* Generate static UI
* Update Delete icon and add tooltip to it
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Move the "delete endpoint" button closer to the element it is attached to
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Generate static UI
* Revert "Move the "delete endpoint" button closer to the element it is attached to"
This reverts commit 4bf895f272.
* Move the "delete endpoint" buttons closer to the elements they are attached to
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Generate static UI
---------
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Make sure to run parallel commands part of a composite command in parallel
* Display warnings in case there are errors when executing pre-stop events
* Fix the command_composite_parallel.go implementation by lowering the case of the sub-command names
Since this passed the Devfile validation logic, we should use the same logic as in command_composite.go
* Display Git commit ID in output of odo commands where the version is displayed
This covers:
- odo init
- odo dev
- odo deploy
Displaying the commit ID (same as in `odo version`) will help quickly pinpoint the exact commit without having to run `odo version`.
See #6131 for more context
* Append the state of the working tree next to the Git commit ID
`git describe` is much more helpful to quickly understand the state of the working tree.
For backward compatibility, we are defaulting to `git rev-parse`,
just in case `git describe` does not work correctly.
* Fix integration tests
* Fix doc automation tests
Strip the Git commit ID from the full odo version string
prior to comparing the outputs.
We still want to compare the tag displayed.
* Add validation to multi-container component
This covers the following forms:
- Add commands when adding a Composite Command
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Add validation to multi-key-value component
This covers the following forms:
- Add Environment variables in Create Container
- Add Deployment annotations in Create Container
- Add Service annotations in Create Container
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Add validation to multi-text component
This covers the following forms:
- Add Command in Create Container
- Add Args in Create Container
- Add Args in Create Image
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Add validation to select-container component
This covers the following forms:
- Select or Create container in Add Exec Command
- Select or create image component in Add Image Command
- Select or create Resource in Add Apply command
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Add validation to volume-mounts component
This covers the following forms:
- Select or Create volume mount in Create container
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Add error helper message for invalid volume size quantities
* Fix Cypress tests
* Generate static UI
* fixup! Add error helper message for invalid volume size quantities
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Generate static UI
---------
Co-authored-by: Philippe Martin <phmartin@redhat.com>
* Fix link to installation page from all release blog posts
* Fix link to installation page mentioned in release blog post template
* Make sure Docusaurus errors out on broken markdown links
This does not entirely fix the issue
with broken links yet (by checking them),
but it is a first step - see [1]
[1] https://github.com/redhat-developer/odo/issues/6617
* Make sure to delete the namespace generated for the test
Otherwise, it might cause name collisions
upon several subsequent runs of the same tests.
* Be more resilient when trying to delete the namespace/project after each test
Do nothing if the namespace/project no longer exists
* Be more resilient when trying to create the namespace/project before each test
Eventually check the existence of the created namespace/project.
* Rename 'helper#GetProjectName' into 'helper#GenerateProjectName'
This makes the intent clearer.
* Make sure to always delete the random namespace/project created when testing project/namespace deletion
This ensures the same local address is used for listening and checking if a given port is free.
Otherwise, `net.listen("tcp", ":$port")` would listen on `0.0.0.0:$port`,
and, on some operating systems like Windows 11, `127.0.0.1:$port` is surprisingly considered as free
(see output below). This, as a consequence, made it impossible to run multiple Dev Sessions on Windows.
```
PS C:\Users\asoro> netstat -aon | grep 2000
TCP 0.0.0.0:20000 0.0.0.0:0 LISTENING 11044
TCP 127.0.0.1:20001 0.0.0.0:0 LISTENING 11044
TCP [::]:20000 [::]:0 LISTENING 11044
TCP [::1]:20000 [::1]:53656 ESTABLISHED 11044
TCP [::1]:53656 [::1]:20000 ESTABLISHED 9984
```
Using the same local address for listening and checking if the port is free would be safer.
If we decide to support passing a custom address, we would use that address instead.
* Set version in build/VERSION file
* Bump version in installation docs
* Add release blog post
* Update release blog content
---------
Co-authored-by: rm3l <rm3l@users.noreply.github.com>
Co-authored-by: Armel Soro <asoro@redhat.com>
* Update main title in README
* Remove extra colon character
* Remove horizontal rules in README
Headings should suffice.
* Display demo video in README
This way, users can have a chance to have a quick preview of odo.
* Make UI not experimental
* Display API and UI URLs
* Remove link to old sources
* Fix integration tests
* Add UI to Usage Data
* Add a "Using the GUI to edit the Devfile" page to doc
* Add link to odo.dev specific page
* Apply suggestions from code review
Co-authored-by: Armel Soro <armel@rm3l.org>
* Change favicon with odo logo
* Display web console URL as part of the Dev status
* Update UI static files
* Document that Comments not supported
* Add UI screenshots
---------
Co-authored-by: Armel Soro <armel@rm3l.org>
* Remove kubeconfig flag
* Do not check file exists from KUBECONFIG, as KUBECONFIG can be a list of files and this is done by clientcmd library
* Fix odo --help
* Add integration test to check flag is not supported
* Add section explaining that users can use Podman without a cluster
* Update sample output of `npx express-generator` in Node.JS guide
* Add section for preparing the target platform with tabs for Podman, Kubernetes and OpenShift
On Podman, this means checking the prerequisites (e.g., min. version of odo, checking that Podman is detected with `odo version`).
On Kubernetes and OpenShift, this is about creating a namespace or project, as before.
* Update sample output for `odo dev` on cluster to reflect the current output
* Add Podman as new tab when running `odo dev` and include sample outputs
* Revert "Update sample output for `odo dev` on cluster to reflect the current output"
This reverts commit 96fb449f715969ddd791e1a5b906408a18bb4364.
* Fix typo in Quickstart intro
* Set Save button on top, enable it only when devfile changed
* Use snackbar to display parse errors
* Do not alert devfile modified when user clicks Save
* Update UI static files
* Update introduction message in Deploy guide
* Fix syntax highlighting for Shell commands
* Bump PrismJS to 1.29.0 to have syntax highlighting for things like Dockerfiles
* Enable syntax highlighting for Dockerfile content in the Deploy guides
* Update instructions on how to login to the container registry
* Add instructions on how to register the image registry in odo
This is to be able to use image selectors.
* Use a relative image name in the Devfile
* Add comment about the ingress domain name variable
* Update the deploy guide for .NET
* Highlight items that need to be changed in the Devfile
* Register the image registry first and make it clear that permissions might need to be updated
To make things simple, use a public registry like ttl.sh that does not require authentication.
* Add more details on how to access the application
* Do not regenerate apiserver-gen/go/routers.go
* Regenerate after changes done in pr#6989
* Do not regenerate apiserver-gen/go/logger.go
* Change logs
* Fix comments
