You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently in version backend-base version 0.0.34 the stackId is not being collected, unlike version 0.0.32 here.
This is because in version 0.32, the CHE_API was accessed to retrieve che-server workspace data.
In contrast, for version 0.34, metadata about devworkspaces are retrieved using a kubernetes client. Currently, the stackId is not available in the devworkspace metadata.
For che-server workspaces, stackIds for che samples come from the attributes.stackName attribute from the response from the CHE_API + "/workspace/" + workspaceId endpoint.
Some examples of stackIds are: Python, Go, Tooling for Apache Camel K, Java Maven etc.
The text was updated successfully, but these errors were encountered:
Currently in version backend-base version 0.0.34 the stackId is not being collected, unlike version 0.0.32 here.
This is because in version 0.32, the
CHE_API
was accessed to retrieve che-server workspace data.In contrast, for version 0.34, metadata about devworkspaces are retrieved using a kubernetes client. Currently, the stackId is not available in the devworkspace metadata.
For che-server workspaces, stackIds for che samples come from the
attributes.stackName
attribute from the response from theCHE_API + "/workspace/" + workspaceId
endpoint.Some examples of stackIds are:
Python
,Go
,Tooling for Apache Camel K
,Java Maven
etc.The text was updated successfully, but these errors were encountered: