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

docs: added more detailed explanation of how to make use of secrets in KeptnTasks #959

Merged
merged 2 commits into from
Mar 2, 2023

Conversation

bacherfl
Copy link
Member

@bacherfl bacherfl commented Mar 2, 2023

Closes #588

@netlify
Copy link

netlify bot commented Mar 2, 2023

Deploy Preview for keptn-lifecycle-toolkit ready!

Name Link
🔨 Latest commit 31c91f3
🔍 Latest deploy log https://app.netlify.com/sites/keptn-lifecycle-toolkit/deploys/6400a228bb516b000879d4fe
😎 Deploy Preview https://deploy-preview-959--keptn-lifecycle-toolkit.netlify.app/docs/tasks/write-tasks
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

Signed-off-by: Florian Bacher <[email protected]>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 2, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@bacherfl bacherfl marked this pull request as ready for review March 2, 2023 13:22
Copy link

@toddbaert toddbaert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems clear to me!

Copy link
Contributor

@thschue thschue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@thschue thschue merged commit 06fa5fd into keptn:main Mar 2, 2023
@keptn-bot keptn-bot mentioned this pull request Mar 2, 2023
Here, the `secret` value is the K8s secret name that will be mounted into the runtime and made available to the function
via the environment variable `SECURE_DATA`.

Here, the `secret` value is the name of the K8s secret containing a field with the key `SECURE_DATA`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are suggestions deliberately disabled here?

I think Kubernetess should be spelled out here rather than K8s

via the environment variable `SECURE_DATA`.

Here, the `secret` value is the name of the K8s secret containing a field with the key `SECURE_DATA`.
The value of that field will then be available to the functions runtime via an environment variable called `SECURE_DATA`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"The value of that field is then available..."

"...to the function runtime..." or "to the functions's runtime" or "to the functions at runtime" -- not sure what is best but this syntax isn't good.

Copy link
Contributor

@StackScribe StackScribe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple word-smithing suggestions but generally it looks good

@keptn-bot keptn-bot mentioned this pull request Mar 16, 2023
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 this pull request may close these issues.

CreateContainerConfigError due to secret
5 participants