console
console copied to clipboard
openshift
Question: urn:alm:descriptor:com.tectonic.ui:select: Value and Label support
Hello,
I couldn't find anywhere else to ask.
This is a question (not an issue) about OLM ClusterServiceVersion configuration.
Specifically, urn:alm:descriptor:com.tectonic.ui:select and how I can define value and label.
Examples only show use of a value that is used in both the UI and to populate the related CRD.
However the source code suggests both value and label are supported.
Looking for pointers/suggestions/etc.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
hey!
not speaking on behalf of Red Hat, but the OKD discussions or #openshift-users on Kubernetes Slack might be a better place to ask questions relating to OpenShift/OKD.
alternatively, if you have a Red Hat OpenShift subscription, you could always open a case
cheers :smile:
/close since it's been four months, feel free to reopen
@logonoff: Closing this issue.
In response to this:
hey!
not speaking on behalf of Red Hat, but the OKD discussions or #openshift-users on Kubernetes Slack might be a better place to ask questions relating to OpenShift.
alternatively, since you have a Red Hat OpenShift subscription, you could always open a case
cheers :smile:
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@logonoff: Reopened this issue.
In response to this:
/reopen
@jhadvig pinging in hopes of an answer :p
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.