Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Return host-info as secret ref #294

Open
Tracked by #330
adrianriobo opened this issue Sep 23, 2024 · 1 comment · May be fixed by #336
Open
Tracked by #330

Return host-info as secret ref #294

adrianriobo opened this issue Sep 23, 2024 · 1 comment · May be fixed by #336
Assignees

Comments

@adrianriobo
Copy link
Collaborator

Currently Tekton tasks are using a workspace named storage to keep the state of the infra + the private key used to connect,

Investigate if we can move to use only results:

  • For infra state we can make use of remote state (s3 / azblob) or check if size for file fits tekton results constraint
  • for private key we should move to results
adrianriobo added a commit to adrianriobo/mapt that referenced this issue Oct 3, 2024
adrianriobo added a commit to adrianriobo/mapt that referenced this issue Oct 3, 2024
adrianriobo added a commit to adrianriobo/mapt that referenced this issue Oct 3, 2024
@adrianriobo adrianriobo self-assigned this Oct 9, 2024
@adrianriobo adrianriobo changed the title Review storage workspace on tekton tasks Return Private keys as Tekton Results Oct 9, 2024
@adrianriobo
Copy link
Collaborator Author

Check the solution where the result is stored as a secret https://github.com/konflux-ci/build-definitions/blob/156fddc4dd952299e97cbb69d68bfaee1f05f72f/task/eaas-provision-space/0.1/eaas-provision-space.yaml#L35

This can be done as a secondary task (openshift only compliant) and we may can use a template mechanism to generate this type of tasks

@adrianriobo adrianriobo changed the title Return Private keys as Tekton Results Return host-info as secret ref Nov 12, 2024
@adrianriobo adrianriobo linked a pull request Nov 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant