-
The Argo metadata field DEPLOYMENT_PLATFORM is currently populated in a wide variety of ways, with different entries for the same ship even at the same DAC. The C17 ICES platform code vocabulary is a…
-
## Description:
"AS A" TC who has invested hundreds of hours entering corrections into the Paratext Interlinearizer, I want to bring those modifications over to ClearDashboard in a bulk import and …
-
If the property:type has value http://schema.org/SoftwareApplication
Is there a way to specify:
- software used
- version of the software (release number, revision number...)
Use-case: action …
-
### What is the issue?
Expose a k8s service on the tailnet, eg:
```yaml
apiVersion: v1
kind: Service
metadata:
name: octobox-server-tailscale
labels:
app: octobox
annotations:
…
-
@noamross you raise an excellent point here that despite a DOI being the *canonical* way to refer to / access a dataset, there really is no well-defined / machine-readable way to determine a download …
-
At the moment when for example a volume is provisioned through CSI it gets assigned a name that is bound to be unique.
Such as pvc-123456789ewqioequwq
This approach works beautifully for a purel…
-
Commands `terraform show` and `terraform state show` are doing the same thing, and I see no reason to keep them separated.
```
✗ terraform show -h
Usage: terraform show [options] [path]
Re…
-
A suggestion from a reviewer reading the document:
https://github.com/ivoa-std/ExecutionPlanner/blob/7f9722546b165c5c950d1c0d834b98183a9c8de1/ExecutionPlanner.tex#L799-L800
> In an ideal world, …
-
This ticket is for pipeline changes that need to occur for the "black box" of the "pre-MGI upstreams" to "post-MGI products" to be produced locally.
Tagging @sierra-moxon @ukemi
kltm updated
2 months ago
-
### Current Terraform Version
```
Terraform v1.0.4
on linux_amd64
```
### Use-cases
A provider output could sometimes be sensitive, but sometimes not. For example: configuration transpilers th…