メモ帳を使ってメモを取ろうとしたら、入力した英単語が勝手に大文字に変換されてしいました。確かにデフォルトその仕様だったことを思い出しました。
その解消方法はとても簡単です。
システム環境設定...
左上のアップルアイコンから「システム環境設定...」画面を開きます。
キーボード/ユーザ辞書の順にクリックします。
デフォルトだと、「文字を自動的に大文字にする」にチェックを入れられています。そのチェックを外して、メモ帳を再起動すれば問題が解消できます。
2019年9月13日金曜日
Macのメモ帳が勝手に先頭文字を大文字に変換する問題
久々自宅用新しいMacを購入しました。
メモ帳を使ってメモを取ろうとしたら、入力した英単語が勝手に大文字に変換されてしいました。確かにデフォルトその仕様だったことを思い出しました。
その解消方法はとても簡単です。
メモ帳を使ってメモを取ろうとしたら、入力した英単語が勝手に大文字に変換されてしいました。確かにデフォルトその仕様だったことを思い出しました。
その解消方法はとても簡単です。
sudoでコマンドを実行しようとしたら、sudo: sorry, you must have a tty to run sudo のエラーが発生しました。
centosでsudoコマンドを実行しようとしたら、以下のエラーがでました。
sudo: sorry, you must have a tty to run sudo
調査したところ、sudoコマンド実行する時にttyが必須と設定されています。
>less /etc/sudores
Defaults requirettyその行をコマンドアウトすれば解決できますが、セキュアではないので、おすすめできません。
必要なユーザーのみ許可した方がいいので、必要なユーザーだけの設定方法は以下の通りになります。ユーザーhogehogeを例とします。
Defaults:hogehoge !requiretty
2019年9月4日水曜日
Terrafom入門編ー設定、及びEC2インスタンスを作成
作業用フォルダを作成
作成するフォルダ名は
terraform_test1を例します。
$mkdir terraform_test1
AWSにアクセス用認証情報を設定
AWSコンソール画面でterraform用IAMユーザーを作成し、accessキーとsecretキーを控えておきます。
terraform.tfvars
というファイルを作成、以下のようにAWSアクセスキーとシークレットキー情報を入れます。PS：terraform.tfvars や、*.auto.fvars というファイル名にしておきば、自動的に変数を読み込んでくれます。
aws_access_key = "AKIXXXXXXXPNN6KXXXXXXX"
aws_secret_key = "6sGivXXXXXXXXXXXbyd1ssLXXXXXY"
aws_secret_key = "6sGivXXXXXXXXXXXbyd1ssLXXXXXY"
EC2インスタンスを作ってみる
ec2.tfというファイルを作成します。中身は以下の通りです。
variable "aws_access_key" {}
variable "aws_secret_key" {}
provider "aws" {
access_key = "${var.aws_access_key}"
secret_key = "${var.aws_secret_key}"
region = "ap-northeast-1"
}
resource "aws_instance" "example" {
ami = "ami-02757f631"
instance_type = "t3.nano"
}
variable "aws_secret_key" {}
provider "aws" {
access_key = "${var.aws_access_key}"
secret_key = "${var.aws_secret_key}"
region = "ap-northeast-1"
}
resource "aws_instance" "example" {
ami = "ami-02757f631"
instance_type = "t3.nano"
}
ami-02757f631をベースにしてインスタンスタイプt3.nanoのEC2一台を作成します。アクセスキーとシークレットキーはterraform.tfvars に設定した値を使用します。初期化
terraform init
コマンドを使って初期化します。
$ terraform initInitializing the backend...Initializing provider plugins...- Checking for available provider plugins...- Downloading plugin for provider "aws" (terraform-providers/aws) 2.25.0...The following providers do not have any version constraints in configuration,so the latest version was installed.To prevent automatic upgrades to new major versions that may contain breakingchanges, it is recommended to add version = "..." constraints to thecorresponding provider blocks in configuration, with the constraint stringssuggested below.* provider.aws: version = "~> 2.25"Terraform has been successfully initialized!You may now begin working with Terraform. Try running "terraform plan" to seeany changes that are required for your infrastructure. All Terraform commandsshould now work.If you ever set or change modules or backend configuration for Terraform,rerun this command to reinitialize your working directory. If you forget, othercommands will detect it and remind you to do so if necessary.
文法チェック
terraform plan コマンドを使って先程作成したec2.tfファイルの正しさをチェックします。$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.
------------------------------------------------------------------------
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# aws_instance.example will be created
+ resource "aws_instance" "example" {
+ ami = "ami-031b61f0c1afb3454"
+ arn = (known after apply)
+ associate_public_ip_address = (known after apply)
+ availability_zone = (known after apply)
+ cpu_core_count = (known after apply)
+ cpu_threads_per_core = (known after apply)
+ get_password_data = false
+ host_id = (known after apply)
+ id = (known after apply)
+ instance_state = (known after apply)
+ instance_type = "t3.nano"
+ ipv6_address_count = (known after apply)
+ ipv6_addresses = (known after apply)
+ key_name = (known after apply)
+ network_interface_id = (known after apply)
+ password_data = (known after apply)
+ placement_group = (known after apply)
+ primary_network_interface_id = (known after apply)
+ private_dns = (known after apply)
+ private_ip = (known after apply)
+ public_dns = (known after apply)
+ public_ip = (known after apply)
+ security_groups = (known after apply)
+ source_dest_check = true
+ subnet_id = (known after apply)
+ tenancy = (known after apply)
+ volume_tags = (known after apply)
+ vpc_security_group_ids = (known after apply)
+ ebs_block_device {
+ delete_on_termination = (known after apply)
+ device_name = (known after apply)
+ encrypted = (known after apply)
+ iops = (known after apply)
+ kms_key_id = (known after apply)
+ snapshot_id = (known after apply)
+ volume_id = (known after apply)
+ volume_size = (known after apply)
+ volume_type = (known after apply)
}
+ ephemeral_block_device {
+ device_name = (known after apply)
+ no_device = (known after apply)
+ virtual_name = (known after apply)
}
+ network_interface {
+ delete_on_termination = (known after apply)
+ device_index = (known after apply)
+ network_interface_id = (known after apply)
}
+ root_block_device {
+ delete_on_termination = (known after apply)
+ encrypted = (known after apply)
+ iops = (known after apply)
+ kms_key_id = (known after apply)
+ volume_id = (known after apply)
+ volume_size = (known after apply)
+ volume_type = (known after apply)
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
インスタンスを作成
terraform apply コマンドを使ってインスタンを作成します。$ terraform applyAn execution plan has been generated and is shown below.Resource actions are indicated with the following symbols:+ createTerraform will perform the following actions:# aws_instance.example will be created+ resource "aws_instance" "example" {+ ami = "ami-031b61f0c1afb3454"+ arn = (known after apply)+ associate_public_ip_address = (known after apply)+ availability_zone = (known after apply)+ cpu_core_count = (known after apply)+ cpu_threads_per_core = (known after apply)+ get_password_data = false+ host_id = (known after apply)+ id = (known after apply)+ instance_state = (known after apply)+ instance_type = "t3.nano"+ ipv6_address_count = (known after apply)+ ipv6_addresses = (known after apply)+ key_name = (known after apply)+ network_interface_id = (known after apply)+ password_data = (known after apply)+ placement_group = (known after apply)+ primary_network_interface_id = (known after apply)+ private_dns = (known after apply)+ private_ip = (known after apply)+ public_dns = (known after apply)+ public_ip = (known after apply)+ security_groups = (known after apply)+ source_dest_check = true+ subnet_id = (known after apply)+ tenancy = (known after apply)+ volume_tags = (known after apply)+ vpc_security_group_ids = (known after apply)+ ebs_block_device {+ delete_on_termination = (known after apply)+ device_name = (known after apply)+ encrypted = (known after apply)+ iops = (known after apply)+ kms_key_id = (known after apply)+ snapshot_id = (known after apply)+ volume_id = (known after apply)+ volume_size = (known after apply)+ volume_type = (known after apply)}+ ephemeral_block_device {+ device_name = (known after apply)+ no_device = (known after apply)+ virtual_name = (known after apply)}+ network_interface {+ delete_on_termination = (known after apply)+ device_index = (known after apply)+ network_interface_id = (known after apply)}+ root_block_device {+ delete_on_termination = (known after apply)+ encrypted = (known after apply)+ iops = (known after apply)+ kms_key_id = (known after apply)+ volume_id = (known after apply)+ volume_size = (known after apply)+ volume_type = (known after apply)}}Plan: 1 to add, 0 to change, 0 to destroy.Do you want to perform these actions?Terraform will perform the actions described above.Only 'yes' will be accepted to approve.Enter a value: yesaws_instance.example: Creating...aws_instance.example: Still creating... [10s elapsed]aws_instance.example: Creation complete after 16s [id=i-054c4a5d5f65d7633]Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
作成したインスタンを確認
terraform show コマンドを使ってインスタンを確認します。$ terraform show# aws_instance.example:resource "aws_instance" "example" {ami = "ami-031b61f0c1afb3454"arn = "arn:aws:ec2:ap-northeast-1:994787028884:instance/i-054c4a5d5f65d7633"associate_public_ip_address = trueavailability_zone = "ap-northeast-1a"cpu_core_count = 1cpu_threads_per_core = 2disable_api_termination = falseebs_optimized = falseget_password_data = falseid = "i-054c4a5d5f65d7633"instance_state = "running"instance_type = "t3.nano"ipv6_address_count = 0ipv6_addresses = []monitoring = falseprimary_network_interface_id = "eni-068a1099ebe134ed4"private_dns = "ip-172-31-45-252.ap-northeast-1.compute.internal"private_ip = "172.31.45.252"public_dns = "ec2-13-231-108-188.ap-northeast-1.compute.amazonaws.com"public_ip = "13.231.108.188"security_groups = ["default",]source_dest_check = truesubnet_id = "subnet-8a04efc2"tenancy = "default"volume_tags = {}vpc_security_group_ids = ["sg-3b359644",]credit_specification {cpu_credits = "unlimited"}root_block_device {delete_on_termination = trueencrypted = falseiops = 300volume_id = "vol-03eedb71c41a89002"volume_size = 100volume_type = "gp2"}}
登録:
投稿 (Atom)