Cloud-oriented Life

Cloud Native Technology Improves Lives

Posted on Edited on In , , Word count in article: 3.7k Reading time ≈ 3 mins.

Inconsistency between the Taro CLI and the project’s dependency version

Taro is an open cross-terminal and cross-framework solution that supports the use of React/Vue/Nerv and other frameworks to develop applications such as WeChat/JD/Baidu/Alipay/ByteDance/QQ applet/H5.

Keep the Taro CLI version consistent with the version of Taro related dependencies in the project

Please always pay attention to keep the Taro CLI version consistent with the version of Taro related dependencies in the project.

The inconsistency between the CLI and the project’s dependency version is one of the sources of many problems. For example, if the Taro CLI version is 3.0.8, then the version of Taro-related dependencies must also be 3.0.8. Taro-related package names can be known from this list - https://nervjs.github.io/taro/docs/CONTRIBUTING/#taro-%E7%BB%84%E6%88%90, and the specific dependency versions can be obtained by using the taro info command or through package.json Know.

Read more »

Posted on Edited on In , , , Word count in article: 2.9k Reading time ≈ 3 mins.

Fixing “License is not available, authentication is not possible” in Elasticsearch

Elasticsearch, a powerful search and analytics engine, sometimes encounters licensing issues that prevent proper authentication. This guide will help you fix the “License is not available, authentication is not possible” error by registering, downloading, and activating a license.

Read more »

Posted on Edited on In , , , Word count in article: 6.8k Reading time ≈ 6 mins.

Rendering Kubernetes YAML from Golang (Go)

Pulumi is a Modern Infrastructure as Code (IaC) to create, deploy, and manage infrastructure on any cloud using familiar programming languages and tools.

Pulumi can generate Kubernetes manifests that easily integrate into existing CI/CD workflows with your familiar programming languages.

This article is about how to use Pulumi and Go SDK to manager Namespace and Deployment within Kubernetes (K8S).

Read more »

Posted on Edited on In , , Word count in article: 2.1k Reading time ≈ 2 mins.

pulumi state delete

Deletes a resource from a stack’s state

Synopsis

Deletes a resource from a stack’s state

This command deletes a resource from a stack’s state, as long as it is safe to do so. The resource is specified by its Pulumi URN (use pulumi stack --show-urns to get it).

Resources can’t be deleted if there exist other resources that depend on it or are parented to it. Protected resources will not be deleted unless it is specifically requested using the –force flag.

Make sure that URNs are single-quoted('') to avoid having characters unexpectedly interpreted by the shell.

Example

1
2
3
4
5
6
7
8
# Get resouce URN
$ pulumi stack --show-urns

# Delete by resource URN with single-quoted('')
$ pulumi state delete ‘urn:pulumi:stage::demo::eks:index:Cluster$pulumi:providers:kubernetes::eks-provider’

# Delete with stack dev force, and skip confirmation prompts
$ pulumi state delete -s dev -y --force  ‘urn:pulumi:stage::demo::eks:index:Cluster$pulumi:providers:kubernetes::eks-provider’

Usages

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
$ pulumi state delete -h
Usage:
  pulumi state delete <resource URN> [flags]

Flags:
      --force          Force deletion of protected resources
  -h, --help           help for delete
  -s, --stack string   The name of the stack to operate on. Defaults to the current stack
  -y, --yes            Skip confirmation prompts

Global Flags:
      --color string                 Colorize output. Choices are: always, never, raw, auto (default "auto")
  -C, --cwd string                   Run pulumi as if it had been started in another directory
      --disable-integrity-checking   Disable integrity checking of checkpoint files
  -e, --emoji                        Enable emojis in the output (default true)
      --logflow                      Flow log settings to child processes (like plugins)
      --logtostderr                  Log to stderr instead of to files
      --non-interactive              Disable interactive mode for all commands
      --profiling string             Emit CPU and memory profiles and an execution trace to '[filename].[pid].{cpu,mem,trace}', respectively
      --tracing file:                Emit tracing to the specified endpoint. Use the file: scheme to write tracing data to a local file
  -v, --verbose int                  Enable verbose logging (e.g., v=3); anything >3 is very verbose

References

[1] pulumi state delete | Pulumi - https://www.pulumi.com/docs/reference/cli/pulumi_state_delete/

[2] Pulumi - Modern Infrastructure as Code - https://www.pulumi.com/

[3] pulumi state | Pulumi - https://www.pulumi.com/docs/reference/cli/pulumi_state/

0%