Cloud Edge Summit 2020 臺灣雲端大會 ## From DevOps to GitOps with GitLab ## Cheng Wei Chen 陳正瑋 DevOps Engineer @ 得寬科技 《Effective DevOps 中文版》譯者、GitLab Hero http://chengweichen.com ES ## DevOps Taiwan https://devopstw 11b11cfca96b2a/p14_1.jpg) 圖片來源 https://youtu.be/Usb9iUphT6Y ## GitOps = IaC + MRs + CI/CD ## GitLab說的 ## GitOps = IaC + MRs + CI/CD ## I nfrastructure as Code Infrastructure System Configuration DevOps ## 範例分享  檢查 .gitlab-ci.yml 產生 CI/CD Pipeline Terraform Ansible Vault Repository ![Image](/uploads/documents/a/0

services depends on your Weblate configuration, but can be made to include popular sites such as GitLab, GitHub, Google, Facebook, or Bitbucket or other OAuth 2.0 providers. Notifications Account Profile For Hosted Weblate there is a dedicated push user registered on GitHub, Bitbucket, Codeberg and GitLab (with username weblate named Weblate push user). You need to add this user as a collaborator and key, from the same section of the admin interface. Enter the hostname you are going to access (e.g. gitlab.com), and press Submit. Verify its fingerprint matches the server you added. They are shown in the

可用于登录 Weblate 的各种服务、完全删除您的账户或下载您的用户数据（请参阅 Weblate 用户数据导出）。 ## 备注 服务列表取决于您的 Weblate 配置，但可以设置为包括 GitLab、GitHub、Google、Facebook 或 Bitbucket 或其他 OAuth 2.0 提供商等热门站点。 ![Image](/uploads/documents/c/5/d/b/c git），但对于私有仓库或推送 URL，设置更加复杂并且需要验证。 ## 从 Hosted Weblate 访问仓库 对于 Hosted Weblate，有一个在 GitHub、Bitbucket、Codeberg 和 GitLab 上注册的专用推送用户（用户名 weblate，电子邮件 hosted@weblate.org 和，名为 Weblate push 用户）。您需要将此用户添加为协作者并为其授予对您的仓库的适当权 在第一次访问时自动存储SSH主机密钥，并记住它们以备将来使用。 如果你想在连接到仓库之前验证密钥指纹，在管理界面的同一区域，在添加主机密钥中添加你要访问的服务器的SSH主机密钥。输入你要访问的主机名（例如：gitlab.com），然后点击提交。确认其指纹与你添加的服务器相匹配。 添加的带指纹的密钥显示在确认消息中： Added host key for github.com with fingerprint

(:[0-9]+)? (/~?[A-Za-z0-9.\-]+)+? )\.(?Pbzr|fossil|git|hg|svn) )/~?[A-Za-z0-9.\-]+)*$ gitlab.com/example/pkg.git gitlab.com/example/pkg.git/sub ## 动态判断 通过 HTTP/HTTPS 请求判断 VCS 类型 golang example machine gitlab.com login root password admin default login guest password 123456 ## Git over SSH go get 默认不会使用 SSH 协议 除非动态获取 meta 时明确指定使用 SSH 协议 // module: example.com/pkg repo: gitlab.example.com/example/pkg com/example/pkg ## SSH 配置 ssh-keygen [-t rsa|ecdsa|ed25519|dsa] $HOME/.ssh 目录下生成相应的秘钥对文件 RSA =>id_rsa、id_rsa

#基于原有的 old-tag 创建新 tag（可用于重命名，生成新 tag 后，再删除旧的 tag） ## ★git远程协作开发 远程协作的基本流程： ① 管理员在创建一个空的远程仓库（比如在 gitlab 上创建一个空的项目） ② 管理员创建一个待推送的本地仓库 (3) 管理员关联本地仓库与远程仓库 ④ 管理员在本地仓库中编辑代码，提交代码 ⑤ 管理员推送本地仓库代码到远程仓库 ⑥ 管理员邀请协作成员 rmtRepo https://gitlab.cof-lee.com/username/RemoteRepoName.git # 将本地代码库的当前分支与远程的代码库相关联，远程库在本地的别名设置为 rmtRepo（当前本地分支与远程仓库的分支名称要保持一致）git 用户名及仓库名称要根据实际情况修改，比如： # git remote add rmtRepo https://gitlab.cof-lee.com/cof/pro-1 ★或者成员先创建一个空项目目录，进入目录后再映射仓库到本地 # mkdir my-pro-1 # cd my-pro-1 # git init # git remote add rmtRepo https://gitlab.cof-lee.com/cof/pro-1.git # git fetch rmtRepo 远程分支:本地分支 #在本地新建分支，不会自动切换到该分支，需要手动 checkout 切换 比如：

services depends on your Weblate configuration, but can be made to include popular sites such as GitLab, GitHub, Google, Facebook, or Bitbucket or other OAuth 2.0 providers. Username may only contain letters For Hosted Weblate there is a dedicated push user registered on GitHub, Bitbucket, Codeberg and GitLab (with the username weblate, e-mail hosted@weblate.org and, named Weblate push user). You need to 如果要在连接到仓库之前对密钥指纹进行验证，请从管理界面的同一部分:guilabel: 'add host key '添加你要访问的服务器的 SSH 主机密钥。输入您要访问的主机名（例如 gitlab.com），然后按 Submit。验证其指纹与您添加的服务器匹配。 The added keys with fingerprints are shown in the confirmation

interface. You can do this in the Add host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. After adding it please verify that the fingerprint matches the server you're use VCS to store the translations, it's already within Weblate and you can base on that. ## GitLab New in version 3.9. This just adds a thin layer on top of Git to allow pushing translation changes directly to the repository, while GitLab creates merge request. ## Pushing changes to GitLab as merge request If you are translating a project that is hosted on GitLab and don’t want to push translations

interface. You can do this in the Add host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. After adding it please verify that the fingerprint matches the server you're use VCS to store the translations, it's already within Weblate and you can base on that. ## GitLab New in version 3.9. This just adds a thin layer on top of Git to allow pushing translation changes directly to the repository, while GitLab creates merge request. ## Pushing changes to GitLab as merge request If you are translating a project that is hosted on GitLab and don’t want to push translations

interface. You can do this in the Add host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. After adding it please verify that the fingerprint matches the server you're use VCS to store the translations, it's already within Weblate and you can base on that. ## GitLab New in version 3.9. This just adds a thin layer on top of Git to allow pushing translation changes directly to the repository, while GitLab creates merge request. ## Pushing changes to GitLab as merge request If you are translating a project that is hosted on GitLab and don’t want to push translations

interface. You can do this in the Add host key section. Just enter hostname you are going to access (eg. gitlab.com) and press Submit. After adding it please verify that the fingerprint matches the server you're to store the translations, it's already within Weblate and you can base on that. #### 1.11.8 GitLab New in version 3.9. This just adds a thin layer on top of Git to allow pushing translation changes directly to the repository, while GitLab creates merge request. ## Pushing changes to GitLab as merge request If you are translating a project that is hosted on GitLab and don’t want to push translations