- Tentar Garmin Exppress no Wine
- Investigar ferramentas para analisar fit files
Updating is always a pain, since I don't have garmin express
Hello, | |
I would like to be able to make a custom DSL that is based on set of ther DSL, to further explain myself I will show the problem: | |
We have a base DSL that defines a new VPC on AWS, that code it has all the necessary network settings witha all the subnets settings, DMZ style, security groups, etc | |
Currently we have the base code with all the variables set, so if a team needs to set the new network settings, they will just copy the code, update the ``varibales.tf`` to their needs. | |
This works up to the point when I need to update base terraform syntax, it becomes a tedious and error prone to pass those changes accross all the existent networks. |
--- | |
- hosts: | |
- oracle-db-prod | |
- teg-prd-db | |
become: true | |
vars: | |
oracle_base: "/u01/app/oracle" | |
rman_retention_policy: "RECOVERY WINDOW OF 7 DAYS" |
#!/usr/bin/env bash | |
# Backup script to an offline external drive | |
# | |
# Assumptions: | |
# * The drive is already mounted and it matches the destination | |
# * The encryption is taken care at the drive itself and its decypted before | |
# the script starts | |
# | |
# Is its recomemended to run this script without perfoming any workload |
I hereby claim:
To claim this, I am signing this object:
The problem: https://community.grafana.com/t/integration-with-azure-metrics-variables-not-getting-full-scope/43216 This is part of a litte workaround on using Azure Metrics with Grafana.
You currently simply cannot fected the resources_groups from the KSL on the variables scope. (please tell me if you can)
So This script uses an Azure Subscription ID and pull the data into a sqlite database. From there using the sqlite plugin you can query them.
""" I need Core Number D for decimal values """ | |
from beancount.core.number import Decimal | |
from beancount.ingest import importer | |
from beancount.core import account | |
from beancount.core import amount | |
from beancount.core import flags | |
from beancount.core import data | |
from beancount.core.position import Cost | |
import csv |
https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#updating-statefulsets
There are some cases that you might be trying to update a statefulset and you get this error:
Error: cannot patch "my-statefulset" with kind StatefulSet: StatefulSet.apps "my-statefulset" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden && cannot patch "my-statefulset-tracking" with kind StatefulSet: StatefulSet.apps "my-statefulset-tracking" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden
And while you can diff a file manually beteween you update and the yaml that you can fecth: kubectl -n my-ns get sts my-statefulset -o yaml