studio/people
Archived
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
This repository has been archived on 2026-03-24. You can view files and clone it. You cannot open issues or pull requests or push a commit.
Files
29904ef7b6da86c70aea8fe2157334ce5c133f2e
people/src/helm/env.d/dev/secrets.enc.yaml

71 lines
4.5 KiB
YAML
Raw Normal View History

💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
djangoSecretKey: ENC[AES256_GCM,data:9fOtt8oesY2CUahg972UGldDrqqF6Fa1Tn+bKxNpMbfXppQtPY2Jfu4EWKAaqH07X00=,iv:OC0ggDgCcja6h4IK73jVXZGDE1qp5OJfeNg182DKxQ4=,tag:ITMAWmPxW8lNBvm2Xefw/Q==,type:str]
djangoSuperUserPass: ENC[AES256_GCM,data:mkLVMnc=,iv:qYBUdUwJk422RVm23/6CUKubFtBL+lofynSnkJglNQk=,tag:Md5FPXwCe9kl5BkICHszzg==,type:str]
🔐(helm) add OIDC secrets for dev environment Set OIDC secrets for the dev environment. Please note that we use different secrets between dev and staging. Why? Benoit created two client id, thus we could easily tests Agent Connect feature from the local host and the staging one. The local host is desk.127.0.0.1.nip.io. If this value change at any time, please consider asking Benoit to update the host value linked to the dev client id.
2024-03-18 23:27:30 +01:00
oidc:
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
clientId: ENC[AES256_GCM,data:gcxd+bMz/YdGw/wrCx1HvSOC5pWkUfuLulU4LPEFtMj+z0W8,iv:7enZhQGxQ2voA72bjGWfMl7yf+ArFgQ/eAspAjRa3p0=,tag:A6Im4qDckaPdX8pdS/lyuw==,type:str]
clientSecret: ENC[AES256_GCM,data:AmEnaHhdCzynw1zhPHwotJ+TUI9DJ11X4ScjGzU4ADOyAJeJp8gWLFuU2GG1mWCOBPjtVOEdaN1ZTZNKKHS9qA==,iv:8oIehcSJHiD1a6C7Jv8rJz2ixakQTpOWYRAr7Ifj2yE=,tag:keKNxLl9jChB/pm52gddhA==,type:str]
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
sops:
kms: []
gcp_kms: []
azure_kv: []
hc_vault: []
age:
- recipient: age15fyxdwmg5mvldtqqus87xspuws2u0cpvwheehrtvkexj4tnsqqysw6re2x
enc: |
-----BEGIN AGE ENCRYPTED FILE-----
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
YWdlLWVuY3J5cHRpb24ub3JnL3YxCi0+IFgyNTUxOSAvOGdBRHB1L1RaVVBBb20z
anpzTS9BNHVYYXhISFNKSGRTTHlGWCtWdDNvCk9pdnIwWW9XTG9iWnAySXB6M3Rm
NDFZV3VCVTh2N1poL2RQeUtiU3VIcWcKLS0tIDdyKzRWYmp4WjZGMlg4eGNkdnNQ
NzdGQWtUaWtlS2xneDVUa21ucUJ3SnMKenloUQTumKE0Q8Zp8hLiFwZiGF+78HtB
lt6aEaOgIu2vc4KC1/9iUK+uPhjQC3ajOQ6G2jcRaoR+BFVlxv1Mug==
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
-----END AGE ENCRYPTED FILE-----
- recipient: age16hnlml8yv4ynwy0seer57g8qww075crd0g7nsundz3pj4wk7m3vqftszg7
enc: |
-----BEGIN AGE ENCRYPTED FILE-----
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
YWdlLWVuY3J5cHRpb24ub3JnL3YxCi0+IFgyNTUxOSA1TlZuVTEyVzVHb1djandk
K2FxZGNlZG9vNllMTnVNZ2pZampnd25pOGxVCkJDUi9YcFVrcVcyOEhKWjBob09M
d0hRc0pkUXhPbTNrS0RSN3NJa2dwbkUKLS0tIG5OSUU4R2s3REV5TWd4Ym5zdWln
ZVcySnhYY2JydmVwOCtEZVhOcTNkQlUKhhZK7CE5bPKbqzmQp7mIL3Lmb8+X+8js
PS55Dv9ivffm+XYKh2tjh3At9+FLNfOECwZBC+KrAQQs0W+vBaXWxQ==
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
-----END AGE ENCRYPTED FILE-----
🔧(sops) update secrets Access to anthony's new key
2024-04-05 12:04:20 +02:00
- recipient: age1plkp8td6zzfcavjusmsfrlk54t9vn8jjxm8zaz7cmnr7kzl2nfnsd54hwg
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
enc: |
-----BEGIN AGE ENCRYPTED FILE-----
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
YWdlLWVuY3J5cHRpb24ub3JnL3YxCi0+IFgyNTUxOSBqOWlUazJpNmhOQ0xYQ0pM
aVRia3B6anErRHNDSTFKT1hWZnZ2blZEeGhZCjNkSm5BZ2hEMVA0dGlSTGo5cWd3
U1FZWnNwSkJhSHNRRDc3QVUrakxad2cKLS0tIEV3ZzVVZ0ZJVytKdzFHSEREcHVq
SUtrZXh6TktaUHZqZTdzL3dZbVdiblkKiJliMwXPs/EJVFuEnegqWKvO3axHJEw7
/Y5qgNPN8MDJrcMtDdcFAKkdrUUUhPgzd1jHeNWlw9tPkqgmoNe1/w==
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
-----END AGE ENCRYPTED FILE-----
- recipient: age12g6f5fse25tgrwweleh4jls3qs52hey2edh759smulwmk5lnzadslu2cp3
enc: |
-----BEGIN AGE ENCRYPTED FILE-----
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
YWdlLWVuY3J5cHRpb24ub3JnL3YxCi0+IFgyNTUxOSBWS3YzWjVlazVDRC9iNTM2
K0VYQ2dQclIvVlFFRmlnbXFhUHVneWl0WHdZCnR1Y2RzMGxzWWRxL2ppYXJVUGhO
TGdld0tLaURiYlMwR3ByL1phZTNnN1UKLS0tIFZ3QVUyVlBpNGZjdHBKL3JHNnFU
YklMbW15Mm9EdnVJbkRLb3drekp3Zm8KrzAAV2EKHHkJzpCBerHkqlI122OUNM/o
3gIX838hJgatKKOO1FipeuzOTwlWEVOwP/iBnHnMe/QdJdsk6issqQ==
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
-----END AGE ENCRYPTED FILE-----
- recipient: age1tl80n23wq6zxegupwn70ew0yp225ua5v4dk800x7g2w6pvlxz46qk592pa
enc: |
-----BEGIN AGE ENCRYPTED FILE-----
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
YWdlLWVuY3J5cHRpb24ub3JnL3YxCi0+IFgyNTUxOSBhemxEZWcwTWQrM0lOd2ky
MVNtcGs3UGphSlZleGhtTFh3andSa00xdmhjCml4cGd1bHVYVzk4djA5QndpQ291
Y0tOSlpoMytvRE41WXliMitEUVZ2ZkkKLS0tIGNoK2xCc3FKNXhhbkErbStyQ0lC
VWpzS04rdkJ3M3BqTTY1T2RyTGd6OTgK0sDGDG3R7fDFwhgn6gdYGDUC9kWFk11e
hn69zBqKXvT7jcQoEWASmbRJ0kYTF/Rg9stWASYfCT+dyEkDfVewPw==
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
-----END AGE ENCRYPTED FILE-----
- recipient: age1qy04neuzwpasmvljqrcvhwnf0kz5cpyteze38c8avp0czewskasszv9pyw
enc: |
-----BEGIN AGE ENCRYPTED FILE-----
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
YWdlLWVuY3J5cHRpb24ub3JnL3YxCi0+IFgyNTUxOSAyelo4b05STnFVVGNPNUdH
bDdiQjQ4WkNlY1dacTZRU3ZObEU3WkFyRUFjClRmOFAyeHRoT2U5Rzc1OTRmRjho
bUo5WjljZzNtNVQ5RlhrdmVpYjhuOE0KLS0tIE8zWEUwL3dyWDZvamdKQk1qcDVR
b2g2SFNDMHZvSTNOYUQ0Rms1RlVBem8KacFpoySUpdGChbGU9PHkefzE5WTw5X9g
du7vbHxqE8M3sjH3TvbB7psj9ISQ/mJ15yvFrIvQUaZ1nQf91b2nHg==
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
-----END AGE ENCRYPTED FILE-----
💚(ci) improve secrets for k8s deployment Avoid secrets to be visible from running deployments
2024-06-03 09:34:28 +02:00
lastmodified: "2024-04-23T08:10:56Z"
mac: ENC[AES256_GCM,data:9maAsoIjrdzZUKqmbsv9iOrxlH5rRF0XJ8+UBqldevEHmfSywKyiRtstMTDVBeJXey6Y0D5V88nXtpZKerRWTpcR+lu8gzGzf1nLZ9r72ldInxXuJPmalQIo6Y4MD+hrOzCbq0i6IQWfTlHpVVz4KulFeAsNyJlD3KZPFsuD6pY=,iv:pxJfbVRCDO9ikionNoy0JvGLgPG2HV805wGprQMV4OE=,tag:zhH5HjyrS0cVDl6dG/9SkQ==,type:str]
🚀(helm) prepare staging deployment Thx @rouja for your help on deploying Desk. This commit slightly modifies helm charts and helmfile to prepare the initial project deployment in a staging environment. @rouja updates: - added secrets files for dev and staging environments (dev's one is empty) - disable ingress by default, to avoid any security issue - added an extra chart to benefit from Indie hoster Postgres operator Thx to this commit we deployed a first draft version figured out that the Django session were broken. We are using a cache session engine, and wrongly configure cache backend to local memory. Thus, Django server is not able to resolve the session, and enters in an infinite loop to log-in the user.
2024-03-15 16:04:57 +01:00
pgp: []
unencrypted_suffix: _unencrypted
version: 3.8.1
Reference in New Issue Copy Permalink