aboutsummaryrefslogtreecommitdiff
path: root/pkg/domain/entities/play.go
diff options
context:
space:
mode:
authorcdoern <cdoern@redhat.com>2022-06-07 16:37:59 -0400
committerCharlie Doern <cdoern@redhat.com>2022-07-20 12:55:33 -0400
commit438fef1caa26a1f09cd7be341e854d4bd5726c2b (patch)
treee449aceae653fcce93fe38aa38a60d08a95bda1e /pkg/domain/entities/play.go
parent8c9eff5b12eebe318be1f905562be6a236285caa (diff)
downloadpodman-438fef1caa26a1f09cd7be341e854d4bd5726c2b.tar.gz
podman-438fef1caa26a1f09cd7be341e854d4bd5726c2b.tar.bz2
podman-438fef1caa26a1f09cd7be341e854d4bd5726c2b.zip
kube secret handling for podman play kube
add support for both creating a secret using yaml and mounting a secret as a volume given a yaml file. Kubernetes secrets have a different structure than podman and therefore have to be handeled differently. In this PR, I have introduced the basic usecases of kube secrets with more implementations like env secrets to come! resolves #12396 Signed-off-by: Charlie Doern <cdoern@redhat.com>
Diffstat (limited to 'pkg/domain/entities/play.go')
-rw-r--r--pkg/domain/entities/play.go5
1 files changed, 5 insertions, 0 deletions
diff --git a/pkg/domain/entities/play.go b/pkg/domain/entities/play.go
index 35a5d8a4a..5bb438d7d 100644
--- a/pkg/domain/entities/play.go
+++ b/pkg/domain/entities/play.go
@@ -88,6 +88,7 @@ type PlayKubeReport struct {
// Volumes - volumes created by play kube.
Volumes []PlayKubeVolume
PlayKubeTeardown
+ Secrets []PlaySecret
}
type KubePlayReport = PlayKubeReport
@@ -100,3 +101,7 @@ type PlayKubeTeardown struct {
StopReport []*PodStopReport
RmReport []*PodRmReport
}
+
+type PlaySecret struct {
+ CreateReport *SecretCreateReport
+}