Remove or update globalMemoryLimit in devfiles' meta.yaml
See original GitHub issueIs your task related to a problem? Please describe.
I don’t see any reason to have globalMemoryLimit
attribute in devfile’s meta.yaml like this https://github.com/eclipse-che/che-devfile-registry/blob/master/devfiles/dotnet/meta.yaml#L6
Describe the solution you’d like
If this field isn’t used, let’s go through all devfiles and remove globalMemoryLimit
from meta.yaml
Describe alternatives you’ve considered
If it used somewhere need to validate this value for each devfile.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Chapter 3. Customizing the registries - Red Hat Customer Portal
This section describes how to build an image containing custom devfile and plug-in registry images. The procedure explains how to add a new...
Read more >Defining metadata (meta.yaml) - Conda
All the metadata in the conda-build recipe is specified in the meta.yaml file. See the example below: ... Users may change this by...
Read more >eclipse/che 7.30.0 on GitHub - NewReleases.io
Upgrade VS Code extension Apache Camel to v0.0.32 #19740; Refactor testLibs to use ... Remove or update globalMemoryLimit in devfiles' meta.yaml #19464.
Read more >Devfile v2 and IDE plug-ins - Eclipse Che Blog
Updating from Devfile v1. While the syntax between v1 and v2 yaml definition is close, there is a major change in the DevWorkspace...
Read more >Devfile v2 and IDE plug-ins in Eclipse Che - Medium
Another change in the lifecycle of a workspace is that the project ... For workspaces using devfile v1, Eclipse Che server fetches meta.yaml...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Today we do not have a mechanism to tell the user that they should NOT try to run a Java stack on a 4GB or less Kubernetes node. That was a first step to try to setup that mechanism.
But as of today we are not using it and we are not maintaining that information. At this stage it’s better to remove it.
Fixed by eclipse-che/che-devfile-registry#379