Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Posts by Iizuki
It seems like pods created by a Kubernetes CronJob (or rather Job) are deleted as soon as they fail. This makes it difficult to figure out what went wrong (unless you have Prometheus or some other ...
When writing a dynamic web service, you broadly speaking have two paths: Use an existing web server (e.g. Apache, Nginx or Lighttpd) to handle the "raw" web requests and implement your own cod...
Unlike docker, Podman won't (understandably) use docker hub by default. You can use it explicitly like this: (just using a random example here, it's an OpenAPI linter) podman pull docker.io/dshanl...
Add the following to /etc/containers/registries.conf: unqualified-search-registries = ["docker.io"] [[registry]] location = "docker.io" Now you can pull just like you would in docker: podm...
You're very much on the right track. std::iter::FromIterator trait This trait is indeed what makes it work. In particular, both functions' return types implement the trait: std::result::Result&l...
Ok I got it working again. The issue was that I had updated my kubeconfig file, and the current-context setting had changed. This setting essentially selects which cluster kubectl targets. Now th...
I don't think there exists a straightforward solution. Likely you can achieve this with rules but you'll have to define and finetune them on each of the jobs. (template jobs may help a bit here.) ...
There are a few fields that play into this, but the gist of it is to set the Pod's restartPolicy to Never. This doesn't mean that the Job only tries once. Rather, instead of restarting the containe...
Helm keeps track of releases and their revisions by creating a kubernetes Secret each time a chart is installed, upgraded etc. These are of course useful in case you want to rollback, but they do p...
In a JSON schema, do the required properties need to be a subset of properties? E.g. is this a valid schema, even though cookies isn't mentioned in properties? { "type": "object", "properti...
How to list all available helm charts in a helm repository, preferrably using the native helm CLI tool? This command lists the repos themselves, but I've yet to discover how to list their contents...
A jinja template expression starts and ends with double curly brackets, which the templating engine consumes. But what if you need a single pair of curly brackets left in the output? Something lik...
SAML service provider (and other types as well) metadata XMLs are full of prefixes like md: and ds:. What do these mean? To illustrate my point, here's a sample metadata file from Wikipedia (CC-BY...
How about a library instead? The traditional way of reducing code duplication among separate software packages is to wrap the common bits in a library and use it where ever the functionality is ne...
Looping in Ansible usually produces a neat output of one line per iteration (per host): ... ok: [Arch] => (item=something) ok: [Arch] => (item=something_else) ok: [Arch] => (item=yet_a...
You don't need to do anything. Helm prunes old release secrets once their number exceeds 10. More specifically, helm upgrade command has an integer option --history-max, that allows you to specify...
The prefixes are explained in saml-metadata-2.0-os spec in section 1.1: "Notation" Prefix Explanation saml: This is the SAML V2.0 assertion namespace [SAMLCore]. The prefix is gen...
According to my reading of the JSON Schema Spec, the answer is no. required array can contain elements which are not in the properties dictionary. The example schema in question seems to be valid....
Apparently there just isn't an equivalent of additionalProperties in Ansible. The way around this is to break the dictionary argument into a list of key/value pairs: argument_specs: main: ...
In JSON Schema one can use the additionalProperties key to validate properties whose names are not know. You can still impose restrictions on their type. How to do this in an Ansible role argument...
Turns out I wasn't far off. The dictionary mustn't be quoted. So the following works: - name: Extraction test vars: dictionary: one: 1 two: 2 key_list: - one ...
Ansible's extract filter is supposedly made for use in map, but at the time of writing the documentation doesn't actually show how to use it together with the map filter. The following outputs VAR...
How to delete a local git branch which hasn't been pushed to anywhere, and only exists locally?
Use the quiet parameter: - name: Assertions ansible.builtin.assert: that: - item quiet: true loop: "{{ loop_items }}" vars: loop_items: - true - true ...
You have to search the repo without any filters: $ helm search repo myrepo NAME CHART VERSION APP VERSION DESCRIPTION myrepo/mychart 1.0.0 1.0.0 ...
- ← Previous
- 1
- 2
- 3
- Next →
