Garden supports disabling privileged containers, and some users have configured it (see Discord message) - should we support that for the containerd runtime too?
We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome
Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.
This is blocked until #114 is merged which comes with first initial integration.
Is it possible to add a check if unleash variable is indeed a json, and disable the option of saving it unless it is?
For example, created a variable for a toggle and selected type to be a json, but I've inserted a string instead of a json and was able to save and pull the value.
{'name': 'test', 'payload': {'type': 'json', 'value': 'not a json'}, 'weightType': 'variable', 'enabled': True}
When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.
This means that when new versions of the application are created the unchanged dependencies can't be reused.
It would be a great enhancement if the application code where p
Liquibase Version:
4.1.0
Also latest master
Liquibase Integration & Version:
gradle, unknown version
Liquibase Extension(s) & Version:
Database Vendor & Version:
PostgreSQL: 12.X (occurs on all supported versions)
Operating System Type & Version:
MacOS 11.4 (20F71), but will occur on all supported OSs
A clear and concis
Use CML_TOKEN instead of REPO_TOKEN to
Using #1671 as an example we could add unit tests for the flux create secret git/helm/tls --export commands and validate the YAML output against golden file.
I was thinking that we could extract the eslint config file into his own module so that we can easily reuse this across any OC related repo in the form of eslint extends.
This because we now have the @opencomponents organization and quite few repos, and i
{
"data": {
"labels": {
"Problem URL": "https:///#problems/problemdetails;pid=-240816790436828345_1633506659151V2"
},
"problem": {
"ProblemTitle": "Http monitor global outage",
},
"project": "musicshop",
"service": "carts",
"stage": "production"
},
"id": "d485ea90-e1ef-4ce2-af21-32
Add a description, image, and links to the continuous-delivery topic page so that developers can more easily learn about it.
To associate your repository with the continuous-delivery topic, visit your repo's landing page and select "manage topics."
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
Checklist: