redhat-developer / redhat-developer/mapt
[Enhancement] Review workspace as output placeholder
Open
Nobody has claimed this yet.
component/tekton
enhancement
priority/MEDIUM
size/S
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
This is an opinionated way to define how wokspaces should maintain the host information to be used by other tasks.
Typically we use a secret structure which can be represented as a workspace:
- name: host-info
description: |
ocp secret holding the hsot info credentials. Secret should be accessible to this task.
---
apiVersion: v1
kind: Secret
metadata:
name: XXXX
labels:
app.kubernetes.io/component: XXXX
type: Opaque
data:
host: XXXX
user: XXXX
password: XXXX
key: XXXX
platform: XXXX
os-version: XXXX
arch: XXXX
os: XXXX
mountPath: /opt/host/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no file or test entry point, so first trace how workspaces are defined, mounted, and exposed as task outputs. Review the example Secret structure and the /opt/host/ mount path, then clarify the intended convention and how another task should consume it. Done requires an agreed workspace representation for the listed host fields.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100